Repository navigation
chore(release): fold 22 more PRs into the 5.0.0 notes - #1446
Mikola Lysenko (mikolalysenko) wants to merge 1 commit into
Conversation
Cover the PRs merged to main after #1432's base (1779317..4cb3643): Cargo source replacement and registry = "crates-io" (#338/#455, #386), pnpm lockfile=false (#1074), berry removed descriptors (#1435), yarnrc ${VAR} reads (#1100), CRLF .npmrc append (#1196), Composer vendor-dir cascade and global home (#439/#686, #586), Go +incompatible vex (#484), gem moved BUNDLE_GEMFILE and commented Gemfile revert (#952, #988), Poetry source = "pypi" (#1282) and Hatch path characters (#547). No entries for #1411 (macOS fix to code #1393 added in this release; the #1393 entry already describes the intended behavior), #1426 (perf regression introduced and fixed within 5.0.0) or the CI/test/bench PRs. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Ready for review (burn-down agent)
Generated by Claude Code |
Final review briefWhat it does: Adds 22 more merged fixes to the Risk: low. It only changes the release notes, on a Look here:
Verified:
Changes I made: none. Open question (doesn't block this PR): main has moved past the stated coverage point. Five user-facing fixes landed after Auto-merge is armed, so approving sends this straight to the merge queue. Generated by Claude Code |
Follow-up to #1432. Editing CHANGELOG.md is allowed here: this is release work, not a feature PR.
Coverage
With this PR,
[5.0.0]covers main up to4cb3643ac(#1432's merge). These 22 PRs landed between17793173fand #1432; I re-checked4cb3643ac..origin/mainright before pushing and it was empty. The date stays 2026-10-12.Added to Fixed
replace-withto a directory source) is followed through every config cargo reads, and hosted mode skips crates when crates.io is replaced by an on-disk source (Agent-mode cargo apply patches the wrong copy whencargo vendoruses a custom directory (or apply runs from a workspace member), yet reports success and VEX attests not_affected #338, Hosted cargo scan in acargo vendorproject reports success but breaks every freshcargo build --frozen --offline, and VEX then omits the patch #455).registry = "crates-io"is now pinned (Hosted cargo redirect refuses a crates.io dependency declared with an explicitregistry = "crates-io", treating crates.io as "another registry" #386).redirect_pnpm_lockfile_disabled) (Hosted pnpm scan pins a pnpm-lock.yaml that pnpm is configured to ignore (lockfile=false/lockfile: false), reports success, and lock-only VEX attests not_affected while pnpm installs the upstream package #1074). Berry restore after a member'syarn remove(Hosted yarn berry rollback/remove put back a descriptor thatyarn removedeleted from one workspace member, so everyyarn install --immutablefails YN0028 #1435)..yarnrc.yml${VAR}/YAML reads (Yarn berry PnP refusal misses a live Plug'n'Play project whose.yarnrc.ymlsetsnodeLinkerthrough${VAR}interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100). CRLF.npmrcappend (Hosted npm scan appends allow-remote=all to a CRLF .npmrc with no final newline as "\nallow-remote=all\r", leaving an LF line and a bare-CR ending that socket-patch's own .npmrc planner refuses #1196).vendor-dir(Composer crawler ignores a vendor-dir set in the global Composer config, so scan -g and agent scans report "No packages found" and leave installs unpatched #439, Hosted Composer vex attests not_affected for an unpatched package when config.vendor-dir is absolute or uses ~/ or $HOME/ #686) and the XDG global home (Composer global-home fallback checks ~/.composer before the XDG home, so scan -g finds no Composer 2 global packages when a stale ~/.composer exists and composer isn't on PATH #586).vexof+incompatiblemodules (Agent-mode Go vex omits an applied patch for a +incompatible module (not_applied, exit 1) because it looks up the manifest with a literal "+" while the API key spells it %2B #484).BUNDLE_GEMFILEin another directory (Gem agent crawl ignores thatBUNDLE_GEMFILE=gemfiles/x.gemfilemovesBundler.root, so a relative bundle path resolves to the wrong dir,applypatches the system copy andvexattestsnot_affectedwhile Bundler loads the unpatchedgemfiles/vendor/bundlecopy #952) and revert of a commented Gemfile line (Vendored gem revert restores Gemfile.lock but leaves the Gemfile path: line when that line carries a trailing comment, and no re-run can finish it #988).source = "pypi"with 1.4–2.2 locks (Hosted and vendored Poetry rewrites breakpoetry installon Poetry 1.4–2.2 when the patched dependency is declared withsource = "pypi"("Repository \"pypi\" does not exist."), with no warning #1282) and Hatch paths containing%#;?(Vendored Hatch wiring makes every Hatch install fail when the checkout path contains %XX, # or ; (e.g. a Jenkins "feature%2Fx" workspace), because Hatch's {root:uri} only escapes spaces #547).No entry, on purpose
Checks
scripts/release-lint.sh --stable-only --tag-check: all checks passed.release.py changelog check --version 5.0.0passed.test_release.ChangelogTests: OK.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changelog update for an existing release; no runtime or build behavior changes.
Overview
Extends the
[5.0.0]section inCHANGELOG.mdso release notes cover main through4cb3643ac, documenting 22 fixes that landed after the prior changelog fold (#1432). No application code changes—only release notes.Fixed entries are added or reorganized by ecosystem: Cargo (honor
[source.crates-io] replace-withdirectory sources; pin explicitregistry = "crates-io"), Composer (dedicated subsection—inheritedvendor-dir, XDG global home), Go (vexfor+incompatibleagent patches), npm family (pnpm with lockfile off, Berry restore after memberyarn remove,.yarnrc.ymlinterpolation, CRLF.npmrcappend), RubyGems (Appraisal-styleBUNDLE_GEMFILE, vendored revert when the Gemfile line was commented), and PyPI (Poetrysource = "pypi"on 1.4–2.2 locks, Hatch paths with URL-breaking characters).Reviewed by Cursor Bugbot for commit 2242d85. Configure here.
Generated by Claude Code