Skip to content

Re-pin vendored core to dspack-gen v0.1.2 (0.3.2)#23

Merged
ryandmonk merged 1 commit into
mainfrom
fix/repin-dspack-gen-core-0.1.2
Jul 22, 2026
Merged

Re-pin vendored core to dspack-gen v0.1.2 (0.3.2)#23
ryandmonk merged 1 commit into
mainfrom
fix/repin-dspack-gen-core-0.1.2

Conversation

@ryandmonk

Copy link
Copy Markdown
Contributor

Summary

DX-0 part A: the report-only core-pin-drift check has been red since dspack-gen 0.1.2 shipped. This re-pins the vendored generator core to the exact v0.1.2 release-tag commit and prepares the 0.3.2 patch release.

  • Pin: 374e1cd91f02701c0d4829ece0a79dd9b381f67b (v0.1.1) → c5bfd6de979f811466c6ba1e1c0f978defc4236f (v0.1.2 tag commit, resolved from the tag ref itself). What 0.1.2 brings: contract-declared required props (v0.4 required-props rules) reach the generation-context grammar.
  • Version: 0.3.1 → 0.3.2, with CHANGELOG entry in the established format.
  • Vendor bundle rebuilt via existing npm run build / bundle:core.

Gates run (all green)

  • npm test: 94/94 (includes the golden-context byte-compare against dspack-gen's compiler golden and the network-boundary test)
  • node scripts/check-sync.mjs: 4/4 byte copies in sync
  • node scripts/check-core-pin.mjs: "the pin is exactly the latest release tag"

Diff review

Only package.json (pin + version), package-lock.json (pin, integrity, resolved version 0.1.1→0.1.2; plus npm normalizing the lockfile's stale 0.3.0 header to the current version), and CHANGELOG.md. No golden or fixture churn — the synced fixtures were already at v2.3.0 via #22.

After merge: tag v0.3.2 on the merge commit to trigger the existing OIDC trusted-publishing release workflow (tag==version guard verified).

No documentation cleanup or workflow changes included.

🤖 Generated with Claude Code

The v0.1.2 tag commit (c5bfd6d) brings the compiler change that puts
contract-declared required props (v0.4 required-props rules) into the
generation-context grammar. 0.3.1 served v0.4 contracts from the v0.1.1
core, and the report-only core-pin-drift check had been red since
dspack-gen 0.1.2 shipped. Vendor bundle rebuilt; golden-context
byte-compare, sync checks, and the full suite pass unchanged; the
pin-drift check is green at the latest release tag.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 22, 2026 17:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR re-pins the vendored @aestheticfunction/dspack-gen core to the v0.1.2 tag commit and bumps @aestheticfunction/ds-mcp to v0.3.2, documenting the change in the changelog to support the patch release.

Changes:

  • Bump package version to 0.3.2.
  • Update the @aestheticfunction/dspack-gen git pin to commit c5bfd6d… (v0.1.2).
  • Update package-lock.json and add a 0.3.2 changelog entry describing the re-pin and rationale.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
package.json Bumps package version and updates the pinned @aestheticfunction/dspack-gen commit.
package-lock.json Updates lockfile to reflect the new pinned generator commit/version.
CHANGELOG.md Adds 0.3.2 release notes describing the core re-pin and expected impact.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ryandmonk
ryandmonk merged commit 235b1dd into main Jul 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants