Repository navigation
chore(release): prepare 3.4 - #126
Merged
Merged
Conversation
Pin the publish workflow to tag v3.4: release targets 19.3.4, 20.3.4, 21.3.4 and 22.3.4, each validated against the same-line *.3.3 baseline. The postpublish retention check now expects the 3.x pages 3.4, 3.3, 3.2, 3.1 and 3.0. The workflow test and the AGENTS.md release note follow. Cut the changelog's Unreleased section as 3.4 (2026-10-30) with the packages line, a "Before upgrading" note (no public API removed or renamed; the defaults that change and the deprecated *_CONFIG tokens) and the highlights, and add an empty Unreleased section and the 3.4 compare link. scripts/release-contracts/3.4.json is not part of this change: it is built from the Linux CI artifacts of the first v3.4 tag run. Co-Authored-By: Claude Opus 5.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
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
Prepare release 3.4:
19.3.4·20.3.4·21.3.4·22.3.4, each validated against the same-line*.3.3. Same shape as the 3.3 preparation (#119)..github/workflows/publish-npm.yml: pinned to tagv3.4;releaseTargets('3.4', { baselineSuffix: '3.3' }); artifactssdcorejs-angular-v*-3.4; contract, publish and verify steps use--suffix 3.4 --baseline-suffix 3.3; postpublish buildspublished-pages/3.4and expects the retained 3.x pages3.4,3.3,3.2,3.1,3.0(2.x unchanged); docs commit "docs: publish Angular 22 release 3.4".scripts/publish-npm-workflow.test.mjs: follows the workflow.AGENTS.md: the "Release đang chuẩn bị" note moves tov3.4.CHANGELOG.md:[Unreleased]cut as## [3.4] - 2026-10-30with the packages line, a Before upgrading note (no public API removed or renamed; the defaults that change: settings modal, Restore defaults also restores the inline external filters, a resize-grip click without a change; deprecatedSD_API_CONFIG/SD_CACHE_CONFIG/SD_STORAGE_CONFIG) and Highlights; new empty[Unreleased];[3.4]compare link.Contents of the release: #121, #122, #123, #124, #125 (all already on
main).Not in this PR
scripts/release-contracts/3.4.jsonis built from the Linux CI artifacts of the firstv3.4tag run (AGENTS.md, "Snapshot phải dựng từ artifact Linux của CI"), then pinned in a follow-up PR before the tag is moved and the release publishes.Release steps after merge
v3.4onmainand push it — the firstpublish-npm.ymlrun stops at "Verify all four retained packages" and publishes nothing.sdcorejs-angular-v{19,20,21,22}-3.4artifacts, build3.4.jsonon Node 24.22.1, check it withrelease-package-contract.mjs --compile-consumers, open the "pin the 3.4 contract" PR.Verification
npm run test:scripts: 280/280 (includestest:publish-npm-workflow).npm run test:showcase-changelog: 10/10 (release headings parse).npm run check:sync: green. No library code changes.API consistency
No public API change in this PR (release tooling and docs only).
🤖 Generated with Claude Code