chore: version 0.3.1 — the audited-label-lift release#15
Merged
Conversation
Publish cycle for the ADR-M3-1 amendment's emitter leg (dspack-emit#14, merged as 8d4f54a): the a2ui surface emitter's audited trigger-label lift. Additive behavior (new 'surface-label-lifted' warning code; previously- refused liftable instances now emit with the lifted label; refusals for no-text instances unchanged). 51 tests + pack-and-install smoke green at this commit. Publishing unblocks dspack-gen's dep bump and the full-amendment rerun — the current rerun measures amendment-rules × pre-lift emitter (0.3.0) and its 9 trigger-label gate failures are the liftable class this release projects. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Release/version-bump PR to publish @aestheticfunction/dspack-emit 0.3.1 as part of the audited trigger-label lift publish cycle.
Changes:
- Bump
package.jsonversion from 0.3.0 → 0.3.1. - Update
package-lock.jsonroot package version to 0.3.1.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updates the package version to 0.3.1 for publishing. |
| package-lock.json | Updates the lockfile’s root version to 0.3.1 (but currently contains a root name inconsistency that should be corrected). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The 2.2.0 sync commit (1c8df39) was pushed to feat/audited-label-lift after PR #14 had already merged — it never reached main and was orphaned when the branch was deleted per the hygiene rule. Re-landed here on the release branch, where the current copies belong. Process note: verify a PR is still OPEN before pushing follow-up commits to its branch. json-render goldens regenerated (no diff — governance-side change). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ryandmonk
added a commit
that referenced
this pull request
Jul 4, 2026
…me cycle Copilot's file summary on #15 flagged it: the lockfile root 'name' still carried the pre-rename package name (npm never rewrites it without an install). npm install --package-lock-only regenerates it to @aestheticfunction/dspack-emit; no dependency changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Publish cycle for the ADR-M3-1 amendment's emitter leg (#14, merged): version 0.3.0 → 0.3.1.
Additive behavior: the audited trigger-label lift (
surface-label-liftedwarning; previously-refused liftable instances now emit; no-text refusals byte-unchanged).^0.3.0consumers move deliberately via lockfile, not implicitly.Verified at this commit: 51/51 tests ·
pack-and-installsmoke green (A1–A3 pass, typed errors intact against the packed tarball).Why now: the running amendment rerun consumes the published 0.3.0 (pre-lift) — its 9 trigger-label gate failures are exactly the liftable class this release projects. Publishing + a dspack-gen dep bump enables the full-amendment leg (the third stage of the v0.4-∀ → rules-only → full-amendment measurement).
Merge, then publish from main:
(or drop an npm automation token into ~/.config/dspack-eval.env as NPM_TOKEN and I'll run it.)
🤖 Generated with Claude Code