Bump the Scout and Jimmy agent packages and their self-pins - #284
Merged
Conversation
Both packages' src changed after 0.0.1 was set, so the tool registry refused to publish them and seeding aborted before reaching the tenant's own workflows. Found by running seed against a real hub, and by check:tool-package-freshness reporting both.
6 tasks
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.
Seeding a tenant currently aborts:
Both packages'
src/moved after0.0.1was set, and both pin themselves at that version, so the pin and the manifest agreed while the code underneath them changed — the modecheck:tool-package-pinscannot see andcheck:tool-package-freshnessexists to catch. Found by runningworkbench seedagainst a real hub; the freshness check reported both by name.Bumps each to
0.0.2and updates the self-pin in the same commit.Worth noting the self-pin idiom makes this failure structurally invisible: a package that pins its own name and version has both sides edited by the same person in the same file, so they never disagree while the source moves underneath. That's why this needed a history-aware check rather than a working-tree one.