claude-code - 💡(How to fix) Fix Model fails to update all version locations despite explicit checklist in CLAUDE.md [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46906Fetched 2026-04-12 13:29:59
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
1
Author
Timeline (top)
labeled ×4commented ×2

Root Cause

  • Cache-bust version mismatch = browser serves stale files = features appear broken
  • Display version mismatch = user sees wrong version = can't track what's deployed
  • The model has the checklist, has the memory, has been corrected — and still doesn't execute consistently
  • This is the same root cause as issue #46905 — CLAUDE.md rules are treated as knowledge, not executable constraints
RAW_BUFFERClick to expand / collapse

Problem

The model consistently fails to update version strings in all required locations, even when CLAUDE.md contains an explicit versioning checklist and the user has repeatedly corrected this behavior within the same session.

Specific Failure

CLAUDE.md contains a micro bump checklist:

  1. Update version constant in source (e.g. APP_VERSION)
  2. Update package.json (or equivalent)
  3. Update server health/version endpoints
  4. Regenerate cache-busted assets (build step)
  5. Commit and push

The project has version strings in three places:

  • backend/db.pyAPP_VERSION = "0.2.14" (updated)
  • frontend/index.html → cache-bust params styles.css?v=0.2.14, app.js?v=0.2.14 (updated)
  • frontend/index.html → visible display <span class="app-version">v0.2.12</span> (NOT updated)

The display version controls what the user sees in the UI. The cache-bust version controls whether the browser loads new assets. Both are critical. The model updated some but not all, creating a version mismatch that is visible to the user.

Pattern

This is not a one-time mistake. In this session:

  1. User explained version bumping is critical for cache-busting
  2. Model experienced the consequence (browser served stale JS, feature didn't work)
  3. Model added version checking to CLAUDE.md Self-Check Protocol
  4. Model saved it to persistent memory
  5. Model STILL failed to update all version locations on subsequent changes
  6. User had to correct multiple times within the same conversation

Why This Matters

  • Cache-bust version mismatch = browser serves stale files = features appear broken
  • Display version mismatch = user sees wrong version = can't track what's deployed
  • The model has the checklist, has the memory, has been corrected — and still doesn't execute consistently
  • This is the same root cause as issue #46905 — CLAUDE.md rules are treated as knowledge, not executable constraints

Expected Behavior

When the model bumps a version, it should grep for ALL occurrences of the old version string and update every one. This is a mechanical operation that should never be partial.

Environment

  • Claude Opus 4.6 (1M context)
  • Claude Code VSCode extension
  • Windows 10

extent analysis

TL;DR

The model should be updated to mechanically grep for all occurrences of the old version string and update every one when bumping a version.

Guidance

  • Review the CLAUDE.md checklist to ensure it includes all required locations for version string updates.
  • Verify that the model is correctly implementing the checklist by checking for updates in all locations, including backend/db.py, frontend/index.html (both cache-bust params and visible display).
  • Consider adding automated testing to ensure version string consistency across all locations.
  • Investigate why the model is not treating CLAUDE.md rules as executable constraints, as this appears to be the root cause of the issue.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue seems to be related to the model's inability to consistently execute the version bumping checklist, despite having the necessary knowledge and memory. The root cause appears to be the same as issue #46905, where CLAUDE.md rules are treated as knowledge, not executable constraints.

Recommendation

Apply a workaround by manually verifying and updating all version string locations until the model is updated to mechanically perform this task. This is because the current model behavior is inconsistent and prone to errors, and manual verification can help prevent version mismatches and ensure correct functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING