Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[automated] Merge branch 'release/7.0' => 'release/7.0-staging' #87524

Conversation

dotnet-maestro-bot
Copy link
Contributor

I detected changes in the release/7.0 branch which have not been merged yet to release/7.0-staging. I'm a robot and am configured to help you automatically keep release/7.0-staging up to date, so I've opened this PR.

This PR merges commits made on release/7.0 by the following committers:

  • carlossanlop
  • vseanreesermsft
  • mmitche
  • Jozkee
  • hoyosjs
  • dotnet-bot
  • ajcvickers

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

merge button instructions

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/7.0
git pull --ff-only
git checkout release/7.0-staging
git pull --ff-only
git merge --no-ff release/7.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-to-release/7.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull https://github.com/dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull git@github.com:dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

hoyosjs and others added 24 commits March 31, 2023 01:07
…ypes that implements INullable

CVE-2023-24936: Check type is allowed when deserializing instance types that implements INullable
…LibraryImportGenerator

Adds a "paramName_lastIndexMarshalled" variable to generated code that tracks the index of the last element in a collection that was marshalled. Then in the cleanup stage, we only clean up to that index. This works for single dimensional arrays of non-blittable elements.

For multidimensional arrays, this will fully initialize higher order arrays to simplify the generated logic. It is possible to avoid this and can be considered in a future PR, if we observe users of multi-dimensional arrays observing performance issues.
… and enable delay load of version.dll

`coreclr` delay loads `version.dll` and adds a hook such that it loads from the system directory. In single-file, we lost this behaviour since it uses static library version of `coreclr`. This adds the same mechanism to single-file.
…e loading

Block password-less PKCS12 blobs on X509 certificate loadings/imports and Prevet AIA fetching of non-cert types.
Merge from public release/7.0 to internal/release/7.0 and resolve conflicts if necessary
….0-2023-06-13-1018

Merging internal commits for release/7.0
@ghost
Copy link

ghost commented Jun 13, 2023

Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

I detected changes in the release/7.0 branch which have not been merged yet to release/7.0-staging. I'm a robot and am configured to help you automatically keep release/7.0-staging up to date, so I've opened this PR.

This PR merges commits made on release/7.0 by the following committers:

  • carlossanlop
  • vseanreesermsft
  • mmitche
  • Jozkee
  • hoyosjs
  • dotnet-bot
  • ajcvickers

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

merge button instructions

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/7.0
git pull --ff-only
git checkout release/7.0-staging
git pull --ff-only
git merge --no-ff release/7.0

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-to-release/7.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull https://github.com/dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging
or if you are using SSH
git checkout -b merge/release/7.0-to-release/7.0-staging release/7.0-staging
git pull git@github.com:dotnet-maestro-bot/runtime merge/release/7.0-to-release/7.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-to-release/7.0-staging

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

Author: dotnet-maestro-bot
Assignees: -
Labels:

area-System.Security

Milestone: -

@carlossanlop carlossanlop added area-codeflow for labeling automated codeflow Servicing-approved Approved for servicing release and removed area-System.Security labels Jun 13, 2023
Copy link
Member

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge commit

@carlossanlop carlossanlop self-assigned this Jun 13, 2023
@carlossanlop carlossanlop merged commit 8196212 into dotnet:release/7.0-staging Jun 14, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jul 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-codeflow for labeling automated codeflow Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants