Repository navigation
chore(release): 5.0.0 - #1194
Conversation
Cut the [5.0.0] CHANGELOG section from [Unreleased], adding notes for the 150 PRs merged since the CHANGELOG freeze (#848), and stamp 5.0.0 into Cargo.toml, Cargo.lock and the npm main + platform packages. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
The test copied the live packaging and tagged v4.0.0, so it failed once the tree was stamped 5.0.0. copy_packaging's baseline= keeps it independent of the checkout's version, like the other stamp tests. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
vlt <= 0.0.0-13 ignores vlt.json's registry (and --registry): installs resolve from public npm. The launcher leg only passed there because @socketsecurity/socket-patch@4.0.0 is published; at the unreleased 5.0.0 it cannot resolve. Verified against an unreachable registry: 0.0.0-1, -11, -12, -13 still install, 0.0.0-14 fails ECONNREFUSED. Marks the era non-hermetic in docs/testing/vlt-compatibility.md and adds the derived skip rule for the launcher leg. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
bugbot run Generated by Claude Code |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 75d69ae. Configure here.
Mikola Lysenko (mikolalysenko)
added
the
Ready for review
|
Ready for review (burn-down agent).
Generated by Claude Code |
|
[final reviewer] Reviewed
( Everything else checks out: Leaving the notes edit to the release agent. Once the two entries are in, I'll post the approval brief. Generated by Claude Code |
|
[final reviewer] Disarmed auto-merge on Once the release agent adds them, I'll post the brief and re-arm auto-merge. Generated by Claude Code |
2 participants
Version-bump PR for socket-patch 5.0.0 (runbook:
docs/releasing.mdstep 2).python3 scripts/release.py changelog cut --version 5.0.0— rolls[Unreleased]into## [5.0.0] — 2026-10-09. Before the cut,[Unreleased]was brought up to date with the 150 PRs merged since the CHANGELOG freeze (Write CHANGELOG only when cutting a release #848): 73 new bullets under Breaking / Added / Fixed / Maintenance, Gradle (Full Gradle support in agent, hosted and vendored modes #646) and sbt/Mill/scala-cli (sbt, Mill and scala-cli support in agent, hosted and vendored modes #690) described once in Added, CI/test/refactor-only PRs folded into one Maintenance line.scripts/version-sync.sh 5.0.0— Cargo.toml, Cargo.lock workspace entries, npm main + 14 platform packages, npm lockfile.scripts/release-lint.sh --stable-only --tag-checkpasses locally (coherence, 125-entry[5.0.0]section, nov5.0.0tag).Two tests assumed the tree was at the published 4.0.0 and broke on the bump:
scripts/tests/test_release.pytest_sync_main_on_a_working_tree_stamps_the_newest_tagtaggedv4.0.0over the live packaging; it now stamps a 4.0.0 baseline like the other stamp tests.launcherleg on vlt ≤ 0.0.0-13: those vlt releases ignore the configured registry (vlt.json and--registry) and resolve from public npm, so the leg only passed because 4.0.0 is published. Verified against an unreachable registry (0.0.0-1/-11/-12/-13 install, 0.0.0-14 fails ECONNREFUSED). The era is marked non-hermetic indocs/testing/vlt-compatibility.mdand the derived manifest skips the launcher leg there.After merge, the release is: Actions → Release → Run workflow on
main(optionallydry-run: truefirst), then approve the staged npm packages (platform packages first).Before dispatching, confirm the registry trusted publishers point at the split workflows (
docs/releasing.md→ One-time registry setup): crates.iosocket-patch-core/socket-patch-cli→publish-cargo.yml; npm main + 14 platform packages →publish-npm.yml. Neither workflow has ever run, and this couldn't be verified without registry owner credentials.🤖 Generated with Claude Code
Note
Low Risk
Packaging version sync, changelog cut, and vlt/release test skips only; no new runtime behavior beyond what is already on main.
Overview
Release train step for socket-patch 5.0.0: rolls the accumulated
[Unreleased]notes into a dated## [5.0.0] — 2026-10-09section (breaking CLI/JSON behavior, Gradle/JVM, ecosystem fixes, etc.) and bumps the workspace and npm packaging from 4.0.0 → 5.0.0 (Cargo.toml/Cargo.lock, main@socketsecurity/socket-patchpackage, 14 platform optional packages, and the npm lockfile).Test harness adjustments so CI stays valid on the new tree:
test_sync_main_on_a_working_tree_stamps_the_newest_tagseeds packaging with a 4.0.0 baseline instead of tagging over live 5.0.0 files; vlt ≤ 0.0.0-13 is documented and skipped for the agent launcher leg because those releases ignorevlt.json/--registryand always hit public npm (unpublished launcher version only exists on the harness registry). Addsregistry_config_ignored(), a derived leg rule invlt-leg-manifest.json, and an update todocs/testing/vlt-compatibility.md.Reviewed by Cursor Bugbot for commit 75d69ae. Configure here.
Generated by Claude Code