Auto bump pinned version#130
Merged
Merged
Conversation
mre
reviewed
Nov 20, 2025
thomas-zahner
force-pushed
the
auto-bump-pinned-version
branch
from
cab777a to
9346b3a
Compare
Thanks @katrinafyi for the idea
thomas-zahner
force-pushed
the
auto-bump-pinned-version
branch
2 times, most recently
from
57a2b99 to
8441976
Compare
thomas-zahner
force-pushed
the
auto-bump-pinned-version
branch
2 times, most recently
from
2de6513 to
2d1c280
Compare
Member
Author
|
I've now tested it a bit and it seems to work pretty well. Note, if there is a PR already (created 24h previously and not merged yet) it will fail as observed here. |
Member
Author
|
First scheduled run created this PR successfully. |
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
3 participants
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.
Example run which resulted in this PR. The created PR contained other changes because it was ran from this branch. With the latest commit it should only run on master.
Maybe it would be better to run the workflow in the main repository and create this PR as part of the release workflow?
Closes #127