Repository navigation
chore(main): release 0.11.0 - #186
Merged
Merged
Conversation
Contributor
Author
|
🤖 Created releases: 🌻 |
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
1 participant
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.
🤖 I have created a release beep boop
0.11.0 (2026-10-13)
⚠ BREAKING CHANGES
JOB_LOCK_TIMEOUT_SECONDSis replaced byJOB_LOCK_LEASE_SECONDS(default 300) andJOB_LOCK_MAX_HOLD_SECONDS(default 86400); leaving the old variable set now fails startup with a message naming the new ones. Upgrading from v0.10.0 or earlier: the runningmake upgradeis the OLD script (the shell keeps reading the file it already opened), which recreates the core container under any in-flight job pass, and a pass killed that way holds its lock for a day under the old code. If you runmake up-jobs, runmake down-jobsbefore upgrading andmake up-jobsafter. Ifmake up-jobsafterwards reports a lock HELD with nothing running, clear it once:make local-manage CMD="clear_job_locks --all".🐛 Bug Fixes
This PR was generated with Release Please. See documentation.