fix: refresh pkg.pr.new @810 lockfile integrity - #78
Conversation
pkg.pr.new republished agent-bundle@810 and @agent-bundle/runtime@810 at commit 19ab901. Refresh integrity so npm ci no longer EINTEGRITY, and follow the rewritten rsc-markdown-stream pin from the new tarballs. Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Pin both compiler and runtime to the full 19ab901221cb80ad83b917c7cdbf5eea4e3f3901 commit that #78 already resolved. Package versions, integrity hashes and dependency graph stay identical. Squash-merged under force-delivery: ACCEPT review; windows Package CI/Changeset starved ~37m with no runner (branch unprotected).
Summary
Package CI
npm cifails withEINTEGRITYfor the pkg.pr.new@810preview packages after those tarballs were republished. Live@810still resolves to the same URLs, but the bytes are now commit19ab901(last-modified2026-09-16T22:00:58Z,x-commit-keyScriptedAlchemy:agent-bundle:19ab901221cb80ad83b917c7cdbf5eea4e3f3901), not the5a4ae0abuild recorded in the lockfile.package-lock.jsonnow matches the current tarballs:agent-bundle@810integritysha512-31pzm7CnoFusDdKLLc5Aw1MS72VS/9edLBlxJhkT+9eOuSF6yTWbMODeZVR0oUsBGlNBZ/qa4EQNkXANJUqPow==(3811404 bytes)@agent-bundle/runtime@810integritysha512-6zpWNTtkIy+yBhqcaWzEdTNqUFW5u3c7GiAOclVhInTopvRe5PZnj1PgWdcaNHKfWHTgFsMhWLYXoogUyC1g+Q==@810rsc-markdown-streampin and the preview version (0.0.0-preview-19ab901) were updated so the lockfile matches the new tarball metadataNo product source changes. No changeset:
.changeset/config.jsonchangedFilePatternsdoes not includepackage-lock.json, andchangeset status --since=origin/mainreports nothing to bump.This is the unblocker for Package CI on main (run 35159695338 after #76) and for #77, which will hit the same
EINTEGRITY.Test plan
npm cisucceeds against the updated lockfile (local Node 22.22 / npm 10.9.7)@810packages and the rewrittenrsc-markdown-streampinchangeset status --since=origin/mainpasses without a new changeset