Repository navigation
chore(deps): raise shared package floors to published versions - #30
Merged
Merged
Conversation
Opened by bitbaum/fleet .github/workflows/internal-currency.yml. The fleet's own packages ship features in MINORS, so version-currency.mjs — which judges by major — reports nothing while consumers drift. This is the instrument that sees it, and it opens the fix rather than reporting it. If this PR is red, that is the useful outcome: it names a repo that cannot take the new version, which nothing else in the fleet would have told us.
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.
Raises this repo's floor on Bitbaum-owned npm packages to their published versions.
Why a bot and not a person.
version-currency.mjsjudges dependenciesby their MAJOR, which is right for
nextandreactand wrong for us —we ship features in minors. Measured 2026-09-21,
@bitbaum/ai-kitwas at1.10.0 with ten of fourteen consumers on major 1 but an older minor, so
the ratchet was green while a fix published for everyone reached two repos.
Why now and not "later". Getting a repo current is the cheapest work
in
SHARED.mdand nobody has ever scheduled it. Adoption in this fleethas only ever moved as a side effect of repairing an outage.
If CI is red here, do not just close this. It means this repo cannot
take the published version — the most useful thing a package author can be
told, and nothing else in the fleet would have said it. Fix it here or open
an issue on the package.
Lockfile written by
pnpm install, not hand-patched.Generated by Claude Code