Repository navigation
chore(knowledge): the GraphCompose 2.4.1 pack - #7
Merged
Merged
Conversation
node tools/api-surface/import-bundle.mjs --from graph-compose-knowledge-2.4.1.zip The bundle attached to the v2.4.1 release, checksum verified against the .sha256 beside it: GraphCompose 2.4.1, commit 092a6190. The scheduled pack-freshness job has failed on main since 2.4.1 was published, because the 2.4 pack still described 2.4.0. Nothing callable moved: the public surfaces change only their version stamps, and excluded.json gains two @internal render-pdf handlers (BarcodeMatrices, BarcodeRuns). docs/limitations.md names the new patch. check-pack-freshness: current (2.4.1, latest 2.4.1); knowledge drift passes. Suite 1185 of 1186, the one failure being the nested .claude/worktrees walk that predates this change.
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.
Why
The scheduled pack freshness job has been red on
mainsince GraphCompose 2.4.1 was published: thegraphcompose-2.4pack still described 2.4.0.What changed
skills/versions/graphcompose-2.4/: re-imported fromgraph-compose-knowledge-2.4.1.zip(release asset, SHA-256 verified). The public surfaces change only their version stamps;excluded.jsongains two@Internalrender-pdf handlers (BarcodeMatrices,BarcodeRuns). Nothing callable was added or removed.docs/limitations.md: names 2.4.1 as the newest pack.Verification
node tools/api-surface/check-pack-freshness.mjs→graphcompose-2.4 is current (2.4.1, latest 2.4.1)node scripts/check-knowledge-drift.mjs→ passesnpm test→ 1185 of 1186; the one failure walks local.claude/worktreescheckouts and exists without this change (CI has none).