Repository navigation
chore(release): 5.1.0 notes for #2010 and #2025 - #2038
Conversation
|
Ready for review at
Generated by Claude Code |
#2031 landed on main at 01:23 UTC, after the f5b0374 cut-off these notes were written against, and changes user-visible Go behavior: it completes the go.work handling #2011 introduced (bypassed replaces stay refs; an unread root go.work no longer withholds the root go.mod) and stops the in-memory hosted engine from probing the process cwd for Go workspaces. The other PRs merged since f5b0374 (#2002, #2034, #2035, #2037) change no shipped behavior and need no note. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011f9aeRVgqkQL2WXrHEqeDJ
|
Final review: the 5.1.0 notes were missing #2031, so I pushed #2031 (
The other PRs merged after I re-ran bugbot run Generated by Claude Code |
Co-Authored-By: Claude <noreply@anthropic.com>
|
Five more PRs merged to
Generated by a one-off release-staging routine. Generated by Claude Code |
|
bugbot run Generated by Claude Code |
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 999e5e8. Configure here.
|
Ready for review at
Generated by Claude Code |
Final review briefWhat it does. Release-notes-only PR for 5.1.0: it adds Risk: low. One file, documentation only. It is a Look here
Verified
Changes I made: none. Open questions: The section is still dated Auto-merge is armed, so approving sends this PR straight to the merge queue. Generated by Claude Code |
Follow-up to #2033: two PRs merged while it was in the merge queue
#2010 and #2025 landed on
mainwhile #2033 was queued. They ship in 5.1.0, so they need entries before Release is dispatched. With this PR, the 5.1.0 notes covermainthrough568e376(#2031 added by the final reviewer; #2002, #2034, #2035, #2037 need no note).This PR changes only
CHANGELOG.md(inside## [5.1.0]), and the version stays 5.1.0.vexno longer attests pnpm pins undergitBranchLockfile(vex_pnpm_git_branch_lockfile), nor npm or Bun packages the project patches itself (vex_npm_patched_dependency)redirect_cargo_config_outside_root,redirect_nuget_inherited_config_outside_root,pypi_requirements_outside_root), and vendored writers only claim.socket/vendor/paths anchored at this project. Global runs and projects outside a checkout are unchangedDouble-check: #2025 changes behavior for projects whose workspace root or settings live above the git root, which are now refused or withheld. It could arguably go under
### Changed. The version stays minor either way. All five codes are documented inCLI_CONTRACT.mdonmain.Local checks:
release-lint.sh --stable-only --tag-checkandrelease.py changelog check --version 5.1.0both passed.Maintainer checklist
git log --first-parent 568e376..origin/main, ignoring this PR's own merge commit.main(optionally adry-run: truerun first).@socketsecurity/socket-patchlast.Generated by a one-off release-staging routine.
Generated by Claude Code
Note
Low Risk
Documentation-only
CHANGELOG.mdedits with no runtime or packaging changes.Overview
Updates the
5.1.0section inCHANGELOG.mdso release notes matchmainthrough the planned cut (including items that landed while a prior notes PR was queued).The new Fixed bullets document shipped behavior:
vexwithholding for npm-family pins writers already refuse (#2010); broader Gogo.work/ hosted-engine workspace handling (#2011, #2031); and General git-root scoping that refuses or withholds out-of-repo workspace/config reads and anchors vendored paths (#2025, with the newredirect_*/pypi_requirements_outside_rootcodes).Maintenance notes now mention consolidating the Socket-origin classifier (#2002) and recent test/CI fixes (#2034, #2035, #2037). No code or version bump—release prep only.
Reviewed by Cursor Bugbot for commit 999e5e8. Configure here.
Generated by Claude Code