docs: record published v1.15.0 release - #343
Merged
Merged
Conversation
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.
Purpose
Update canonical product status after the public v1.15.0 release. The release removed the general Usage workspace and bundled
ccusage, and retiredcodevetter usage/quotawith a ContextDaddy migration message. This changes documentation only.Evidence
baa14112with the arm64 DMG, ZIP, and Sparkle appcast.pnpm release:manifest:verify -- --tag v1.15.0reportsqualified: true, 3/3 expected assets, no blockers.node scripts/check-docs.mjsandgit diff --checkpassed.After merge, redeploy the landing page so public docs and
/downloadread the published release feed and this current status.Updates #328. ContextDaddy's installed usage/allowance parity remains a separate qualification item.