Skip to content

After 1.5.0: lock the published signer packages; CI runs the 1.5.0 verifier - #470

Merged
LoopGlitch26 merged 2 commits into
mainfrom
agent/issue-150-lock
Oct 28, 2026
Merged

LoopGlitch26 merged 2 commits into
mainfrom
agent/issue-150-lock

Conversation

@LoopGlitch26

Copy link
Copy Markdown
Member

RELEASING step 5 for 1.5.0. The four @cygnuxlabs/tracekit-signer-* entries in sdk/typescript/package-lock.json are locked at 1.5.0 with npm's tarball and integrity for each (checked against npm view), so npm ci (release-dry-run, the next release's build) installs again; checked locally with npm ci. v1.5.0 joins RELEASED in tests/test_released_verifiers.py, so CI runs this release's verifier on every later signer's bundles.

RELEASING step 5: v1.5.0 joins RELEASED in tests/test_released_verifiers.py. The signer packages are locked in sdk/typescript/package-lock.json in the next commit, once npm has published them.

Signed-off-by: LoopGlitch26 <53336715+LoopGlitch26@users.noreply.github.com>
RELEASING step 5: the four @cygnuxlabs/tracekit-signer-* entries are locked at 1.5.0 with npm's tarball and integrity, so `npm ci` (release-dry-run, the next release's build) installs again.

Signed-off-by: LoopGlitch26 <53336715+LoopGlitch26@users.noreply.github.com>
@LoopGlitch26
LoopGlitch26 enabled auto-merge (squash) October 28, 2026 13:40
@LoopGlitch26
LoopGlitch26 merged commit 988e6bb into main Oct 28, 2026
31 of 32 checks passed
@LoopGlitch26
LoopGlitch26 deleted the agent/issue-150-lock branch October 28, 2026 14:20
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.

1 participant