feat: maintain full changelog history while publishing truncated version - W-21787149#7659
Draft
madhur310 wants to merge 6 commits into
Draft
feat: maintain full changelog history while publishing truncated version - W-21787149#7659madhur310 wants to merge 6 commits into
madhur310 wants to merge 6 commits into
Conversation
- Remove 4 temporary CHANGELOG backup files (created by restoration script) - Revert .claude/skills/changelog/SKILL.md to correct state - The doc incorrectly referenced 'conventional-changelog-action' but we use custom scripts Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
madhur310
changed the title
…on merge Changed from complex backup/restore approach to cleaner design: Before: - Generate changelog → prepend to full history on release branch - During packaging: backup → truncate → package → restore - Full history maintained on release branch throughout After: - Generate changelog → writes ONLY new release (on release branch) - Package directly (no truncation needed - already small) - On merge to develop: prepend new section to develop's full history Benefits: - Simpler packaging (no backup/restore dance) - Clearer release branch (only shows what's new) - Single prepend operation (on merge, not every build) - Separation of concerns (release = new, develop = full history) Changes: - Reverted change-log-generator-utils.js to replace mode - Removed marketplace prep scripts (no longer needed) - Updated buildAll.yml (removed prepare/restore steps) - Added prepend-release-changelog.js (prepends on merge) - Updated mergeReleaseBranch.yml (runs prepend script) - Updated documentation Co-Authored-By: Claude Sonnet 4.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.
What does this PR do?
Implements a changelog strategy that maintains full historical changelog on the
developbranch while keeping release branches small and marketplace-ready.How it works:
Key changes:
Result:
What issues does this PR fix or reference?
Fixes the issue where CHANGELOG.md was truncated each week, losing all historical release notes from the repository. History was only accessible via GitHub releases.
Functionality Before
On develop:
On release branch:
During packaging:
Functionality After
On develop:
On release branch:
During packaging:
Example flow:
Create release branch from develop (3,811 lines)
└─> Generate changelog replaces with ~50 lines (new release)
Package & publish
└─> VSIX contains ~50 lines ✅
Merge release → main → develop
└─> Script prepends ~50 lines to develop's 3,811
└─> Develop now has 3,860 lines (history grows)
Next week repeats from step 1
Technical Details
One-time restoration:
Automated prepending:
prepend-release-changelog.jsto prepend new release to develop's history@W-21787149@