Mergify and actions upgrades #10260
Merged
Mergify and actions upgrades #10260
Conversation
This file contains 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
geekosaur
force-pushed
the
mergify-actions-upgrades
branch
from
09e4a83 to
bca9211
Compare
|
I did a quick audit of the other actions we use in our workflows; it looks like only |
|
BTW, the summary still complains about the configuration. This is because it uses the Mergify configuration on |
Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules
geekosaur
force-pushed
the
mergify-actions-upgrades
branch
from
bca9211 to
bcaa508
Compare
ulysses4ever
approved these changes
Aug 16, 2024
There was a problem hiding this comment.
Thanks!
Some unfortunate repetition with Mikolaj but that's not an issue: we can't have too much @Mikolaj!!!
|
Sadly, while there is a |
This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4.
geekosaur
force-pushed
the
mergify-actions-upgrades
branch
from
9b13595 to
c7ac80c
Compare
Mikolaj
approved these changes
Aug 17, 2024
geekosaur
added
squash+merge me
mergify
bot
added
the
merge delay passed
2 tasks
geekosaur
added a commit
that referenced
this pull request
Aug 22, 2024
mergify bot
added a commit
that referenced
this pull request
Aug 24, 2024
* implement mergify rules for release branches We only handled the case of backports previously, but the current release checklist expects that we can commit PRs to release branches during a release (e.g. changelogs, because we want the list of changelog.d files that are actually part of the release). * block merging if PR has a 'blocked:' label * update backports strategy for #10260 --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
This was referenced Aug 26, 2024
|
@mergify backport 3.12 |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Aug 30, 2024
* upgrade actions/upload-artifact to v4 * update Mergify queue strategies Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules * update actions/download-artifact This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4. --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 75711fc) # Conflicts: # .github/mergify.yml # .github/workflows/validate.yml
2 tasks
geekosaur
added a commit
that referenced
this pull request
Aug 30, 2024
* upgrade actions/upload-artifact to v4 * update Mergify queue strategies Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules * update actions/download-artifact This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4. --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 75711fc)
geekosaur
added a commit
that referenced
this pull request
Aug 30, 2024
* upgrade actions/upload-artifact to v4 * update Mergify queue strategies Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules * update actions/download-artifact This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4. --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 75711fc)
geekosaur
added a commit
that referenced
this pull request
Sep 13, 2024
* upgrade actions/upload-artifact to v4 * update Mergify queue strategies Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules * update actions/download-artifact This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4. --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 75711fc)
Mikolaj
pushed a commit
that referenced
this pull request
Sep 13, 2024
* upgrade actions/upload-artifact to v4 * update Mergify queue strategies Mergify is requiring that separate queues be used for different merge strategies, staerting in mid-September with a brownout in mid-August. https://docs.mergify.com/configuration/file-format/#queue-rules * update actions/download-artifact This one wasn't throwing warnings, but has also been updated with the same deprecation timeframe. It's also incompatible with actions/upload-artifact@v4. --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 75711fc)
mergify bot
added a commit
that referenced
this pull request
Sep 13, 2024
Mergify and actions upgrades (backport #10260)
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.
Mergify is requiring different queues for different merge strategies as of mid-September.
actions/upload-artifact@v3andactions/download-artifact@v3are being removed in November.Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: