docs: drop the Status column from CWS version history - #49
Merged
Merged
Conversation
In practice a submission follows the version bump almost immediately, so Draft was never a real state and Submitted/Published needed a follow-up edit each release just to flip one word (see PR #48). Date already says roughly when a version went out, and actual rejections have their own section further down -- the column wasn't carrying information those didn't already cover. Also documents in RELEASE.md that the version bump + version-history row belong in the same pre-merge commit/PR as the change they describe, since tag-release.yml reads manifest.json's version at merge time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
cws/CHROMEWEBSTORE.md's Version History table. In practice submission follows the version bump almost immediately, so Draft was never a real state, and the column needed a follow-up PR each release just to flip one word (as in docs: mark v2.2.0 as submitted in CWS version history #48). Date already conveys roughly when a version shipped, and actual rejections have their own dedicated section.RELEASE.md's pre-merge checklist to make explicit that the version bump and the version-history row land together, in the same commit/PR as the change they describe.Test plan