docs: close out v1.0.11 (tagged + released) - #69
Merged
Conversation
Records the release, the prod verification including the original bug driven in real Chrome, and the two fixes found while closing out -- the vercel preview prefix that was our own config rather than the platform, and the CI concurrency setting that let three commits reach production with cancelled as their only verdict.
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
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.
Closes the v1.0.11 slice, matching the pattern used for v1.0.9 and v1.0.10.
⏸️ untagged→✅ shipped; final exit criterion ticked with the release date and a note on why docs: complete the [1.0.11] changelog before tagging #68 was needed (release.ymlpublishes the changelog section verbatim, and fix(vercel): disable previews for release/ and other unlisted branch prefixes #66/ci: stop cancelling in-progress runs on main (3 commits shipped unverified) #67 merged after the release-prep PR).Also records two things worth not relearning:
Vercelcheck was our config, not the platform —release/**missing fromvercel.ts's prefix list. I had guessed at an unprovisioned preview environment before reading the file. The note spells out why the two tidier-looking fixes (deploymentEnabled: false,'*': false) would both kill production deploys.mainand production withcancelledas their only verdict. Nothing shipped broken, but they were individually unverified. Caused by my own batch merge; the config permitted it silently.Docs only.