fix(release): unjam v1.3.180 publish — consolidate orphaned upgrade fragments + fix stale eli16#646
Open
JKHeadley wants to merge 1 commit into
Open
fix(release): unjam v1.3.180 publish — consolidate orphaned upgrade fragments + fix stale eli16#646JKHeadley wants to merge 1 commit into
JKHeadley wants to merge 1 commit into
Conversation
…ragments into NEXT.md + fix stale NEXT.eli16.md The npm publish has failed on every merge since 1.3.179: #639, #640, #641, #642 are merged but unreleased. Root cause = the release "check upgrade guide" gate. Each PR wrote its own NEXT.md, so the metrics (#639/#640) and restart-immediately (#641) guides were left ORPHANED in upgrades/next/ while #642 overwrote NEXT.md — and NEXT.eli16.md went stale (old post-mortem content, missing required sections). Earlier runs also failed on inline code in "What to Tell Your User". Fix (docs-only): - Consolidate all four changes (metrics ledger + funnel tap, restartImmediately, PromiseBeacon a2a-reply de-flood) into a single clean NEXT.md. "What to Tell Your User" is plain prose — no inline code, no config keys (validator rule). - Rewrite NEXT.eli16.md to match 1.3.180 with the required sections. - Remove the three now-folded-in upgrades/next/ fragments. Verified: validateGuideContent → CLEAN for NEXT.md + NEXT.eli16.md; the full check-upgrade-guide.js finalize+validate at v1.3.180 passes (exit 0). This ships all four merged PRs' narratives in one 1.3.180 guide and unblocks the fleet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Unjams the npm publish. #639, #640, #641, #642 are all merged but unreleased — npm is stuck at 1.3.179 — because the release "check upgrade guide" gate has failed on every merge since.
Root cause (#42 in the wild)
Each PR wrote its own
upgrades/NEXT.md, so they overwrote instead of accumulating:upgrades/next/and never assembled into NEXT.md.#642overwrote NEXT.md with just its PromiseBeacon guide.NEXT.eli16.mdwent stale (old post-mortem content, missing required sections).Fix (docs-only — no ship-gate)
NEXT.md(metrics ledger + funnel tap,restartImmediately, PromiseBeacon a2a-reply de-flood). "What to Tell Your User" is plain prose — no inline code, no config keys.NEXT.eli16.mdto match 1.3.180 with the required sections.upgrades/next/fragments.Verification
validateGuideContent→ CLEAN for both NEXT.md and NEXT.eli16.md.check-upgrade-guide.jsfinalize+validate at v1.3.180 → exit 0 ("✓ Upgrade guide finalized and validated for v1.3.180").Merging this triggers the publish on a clean main → 1.3.180 ships all four merged PRs (including the restart-immediately flag and the metrics) to the fleet. Follow-up: the structural #42 fix (fragments should accumulate, not overwrite; validate at fragment-commit time).
🤖 Generated with Claude Code