CLAUDE CODE V2.0.75 PUBLISHED WITHOUT GITHUB RELEASE NOTES
Anthropic’s Claude Code v2.0.75 is on npm but lacks a corresponding GitHub release/tag, so the /release-notes command only shows up to v2.0.74. This is a regres...
Anthropic’s Claude Code v2.0.75 is on npm but lacks a corresponding GitHub release/tag, so the /release-notes command only shows up to v2.0.74. This is a regression seen in prior versions and breaks standard changelog-based upgrade workflows. Treat 2.0.75 as untracked until release notes appear or pin to the last tagged version.
Missing release notes/tags hinder auditability, SBOM accuracy, and change risk assessment.
Automated upgraders pulling latest may introduce opaque changes and break builds.
-
terminal
Install 2.0.75 in a sandbox, verify cli version, and confirm /release-notes behavior; ensure pipelines fail or warn when release notes are missing.
-
terminal
Update Dependabot/Renovate rules to hold 2.0.75 or require manual approval until a GitHub release appears.
Legacy codebase integration strategies...
- 01.
Pin to 2.0.74 (or last tagged version) in lockfiles and CI until 2.0.75 has a release tag and notes.
- 02.
Harden scripts that parse GitHub releases to handle missing entries without failing and keep SBOM/changelog generation consistent.
Fresh architecture paradigms...
- 01.
Adopt a policy that AI tool upgrades require a GitHub release/tag and changelog; enforce via CI checks.
- 02.
Use dist-tags and lockfiles with canary rollouts to avoid untracked updates from npm.