fix: restore the version after a concurrent-merge regression (v0.320.1) - #589
Merged
Conversation
#588 branched off v0.319.0 and bumped to v0.319.1. #585 merged v0.320.0 in the meantime, so #588's squash carried its own package.json back over it: main landed on 0.319.1 with 0.320.0's code in it, and the CHANGELOG listed 0.319.1 above 0.320.0. The live instapods box then reported 0.319.1 while running both changes. That matters because the sidebar/`/health` version is how we tell which build a long-running server is holding in memory — the first thing checked when a change "isn't taking". A version that moves backwards makes that check lie. Renames the 0.319.1 heading to 0.320.1 (the patch on top of 0.320.0, which is what the code actually is), bumps package.json to match, and updates the Step 0 reference in docs/insights-revisit.md. No code change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AiTKjtdcF4ESbuYVWj2CfU
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#588 branched off v0.319.0 and bumped to v0.319.1. #585 merged v0.320.0 while it was open, so #588's squash carried its own
package.jsonback over it — main landed on 0.319.1 with 0.320.0's code in it, and the CHANGELOG listed 0.319.1 above 0.320.0. The live instapods box reported0.319.1while running both changes.That matters because
/health+ the sidebar version is how we tell which build a long-running server is holding in memory — the first thing checked when a change "isn't taking". A version that moves backwards makes that check lie.[0.319.1]heading →[0.320.1](the patch on top of 0.320.0, which is what the code actually is)package.json→ 0.320.1docs/insights-revisit.mdupdatedNo code change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AiTKjtdcF4ESbuYVWj2CfU