Skip to content

Conversation

@thomas-zahner
Copy link
Member

@thomas-zahner thomas-zahner commented Nov 20, 2025

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

@thomas-zahner thomas-zahner force-pushed the auto-bump-pinned-version branch from cab777a to 9346b3a Compare December 10, 2025 15:16
@thomas-zahner thomas-zahner force-pushed the auto-bump-pinned-version branch 2 times, most recently from 57a2b99 to 8441976 Compare December 10, 2025 17:04
@thomas-zahner thomas-zahner force-pushed the auto-bump-pinned-version branch 2 times, most recently from 2de6513 to 2d1c280 Compare December 10, 2025 17:16
@thomas-zahner
Copy link
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.

@thomas-zahner thomas-zahner merged commit 48a127f into master Dec 10, 2025
1 of 2 checks passed
@thomas-zahner thomas-zahner deleted the auto-bump-pinned-version branch December 10, 2025 17:21
@thomas-zahner
Copy link
Member Author

First scheduled run created this PR successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workflow for updating pinned version

4 participants