chore(deps): chant 0.72.1 - #60
Merged
Merged
Conversation
Two releases behind: the pin was ^0.71.1, which does not resolve to any 0.72.x, so nothing from 0.72.0 or 0.72.1 had reached this repository. What the range now admits that it did not: foldProject's lexicon list and build parameters (chant#2422), the SPEC_VERSION export (chant#2424), a unit-level fold binding the file's own functions (chant#2436), a project-local call admitted by the shape classifier (chant#2435), and a host package named outside the lexicon convention (chant#2438). The lexicon dependencies move with it, since chant releases the lexicons in lockstep and ^0.72.1 on core would otherwise sit beside 0.71.1 lexicons peering on ^0.71.1. Gates: tsc clean, tests passing, production build clean, and the built CLI runs — the last of those because a missing transitive dependency is invisible until runtime, which is how chant-v0.71.0's undeclared js-yaml reached all three wardens.
`action/index.mjs` is a committed build artifact and CI gates that it matches a fresh `npm run build:action`, so a dependency bump that changes bundled code has to carry the rebuild with it. Missing this is what turned the bump red rather than anything wrong with the bump. The diff is chant's own change, inlined: `findCompositeDefinition` and `resolveInterpretableFactory` threading `hostForm`, and `interpretCompositeFactory` returning a host's members unwrapped (chant#2442). Plus the dependency strings in the embedded package metadata. Verified the rebuilt bundle runs: it reports the missing required `config` input, which is the action's own argument handling rather than a load failure.
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.
Two chant releases behind. The pin was
^0.71.1, which does not resolve to any 0.72.x, so nothing from 0.72.0 or 0.72.1 had reached this repository.What the range now admits
foldProject's lexicon list and build parameters (chant#2422)SPEC_VERSIONexport (chant#2424)The lexicon dependency moves with it, since chant releases the lexicons in lockstep and
^0.72.1on core would otherwise sit beside a 0.71.1 lexicon peering on^0.71.1.Gates
tsc clean, 553 tests passing, production build clean, and the built CLI runs.
That last one is deliberate rather than ceremonial: a missing transitive dependency is invisible to tsc and to the unit tests, and only appears at runtime. That is exactly how chant-v0.71.0's undeclared
js-yamlreached all three wardens and broke their production builds. chant now gates it repo-side (packages/core/src/meta/declared-imports.test.ts), but running the bundle here is the check that would have caught it downstream.