Repository navigation
image: construct-brand at r5 in the lock, and a test that the locks follow the recipes - #47
Merged
Merged
Conversation
The epoch was raised in os#45 without task lock, so apko on the release builder refused the r5 it built against the lock's r4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TestChangedRecipesBumpVersionOrEpoch asks for a new version or epoch, and nothing checked that the lock followed: the release builder found construct-brand at r5 against the lock's r4. The test fails it on the pull request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The release failed in
test:usb→rootfs:#45 raised the epoch without running
task lock, which AGENTS.md requires for a changed recipe.task build -- construct-brand, thentask lock: the diff is onlyconstruct-brand=0_git20261005-r5inimage/apko.lock.yaml; both roots built, andcheck-lockpassed forrootfs.tarandinitrd.tar.TestLocksPinRecipesAtTheirBuild: every package a lock pins underrecipes/' packagesthat is a recipe's own package is pinned at that recipe'sversion-r<epoch>. It fails against main's lock ("pins construct-brand=0_git20261005-r4, its recipe builds 0_git20261005-r5") and passes with this one.task checkpasses.Subpackages are not compared: their names do not always start with their recipe's name.
🤖 Generated with Claude Code