feat: show changelog after extension update - #83
Draft
molvqingtai wants to merge 10 commits into
Draft
Conversation
molvqingtai
changed the title
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.
Goal
Show the relevant changelog after an eligible extension update so users can review the release they just received.
Scope
This branch/PR is the complete delivery for the update-changelog-page requirement: OpenSpec, source implementation, focused regression coverage, full implementation test evidence, and same-requirement repairs.
Key behavior
Non-goals
Validation
The implementation must establish parent FAIL-before coverage, freeze one source exact, and run same-exact
pnpm testbefore review.Current status
Draft. Source implementation task #375 is in progress on this same branch. No merge authorization.