[Auto-generated] Merge main into release/3.19.0#2458
Merged
phargogh merged 5 commits intorelease/3.19.0from Mar 25, 2026
Merged
[Auto-generated] Merge main into release/3.19.0#2458phargogh merged 5 commits intorelease/3.19.0from
phargogh merged 5 commits intorelease/3.19.0from
Conversation
Update codesigning service
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge
mainintorelease/3.19.0This PR has been triggered in an effort to update
release/3.19.0with thechanges that were just added to
mainin this commit.If there aren't any conflicts and tests pass
Great, merge away!
If there are merge conflicts
You (as a software team member) have write access to this branch
(
autopr/main-rev2fdc5fd-into-release-3.19.0) on this repo. This means you can address any mergeconflicts directly either by:
(see below for an example of how to do this)
If tests fail or there are problems with the merge
This is unlikely, but it can happen. To fix issues, make the changes you need
to make on your fork and push the changes up to this branch. See below for an
example of how to do this.
To push changes to this branch
In your fork, run:
All changes pushed in this way will appear in this PR.
This PR was created because there was a push to
mainthat triggered this workflow, which is defined at.github/workflows/autopr-create.yml. This workflow was triggered byphargoghwith the eventpush.