Repository navigation
chore(release): prepare 3.3 - #119
Merged
Merged
Conversation
Pin the publish workflow to tag v3.3: release targets 19.3.3, 20.3.3, 21.3.3 and 22.3.3, each validated against the same-line *.3.2 baseline. The postpublish retention check now expects the 3.x pages 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.3 (2026-10-29) with the packages line, and add an empty Unreleased section and the 3.3 compare link. scripts/release-contracts/3.3.json is not part of this change: it is built from the Linux CI artifacts of the first v3.3 tag run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 29, 2026
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.
Summary
Prepares release
v3.3:19.3.3·20.3.3·21.3.3·22.3.3, each validated against the same-line*.3.2baseline..github/workflows/publish-npm.yml: tagv3.3,releaseTargets('3.3', { baselineSuffix: '3.2' }), artifact names,--suffix 3.3 --baseline-suffix 3.2, postpublish retention check3.3,3.2,3.1,3.0and the docs commit message.scripts/publish-npm-workflow.test.mjs: the same pins.AGENTS.md: the "Release đang chuẩn bị" note.CHANGELOG.md:[Unreleased]is cut as## [3.3] - 2026-10-29with the packages line; an empty[Unreleased]and the[3.3]compare link are added. The section content is unchanged (fix(chip): apply removable on every path and use one error gate (CH1) #103–feat(table): loading layer without an overlay (skeleton rows, delayed progress bar) #118).The release has consumer-breaking changes (chip, upload file, table loading). As in 3.1 and 3.2, they ship as a suffix bump with the Changed (BREAKING for consumers) section.
Not in this PR
scripts/release-contracts/3.3.json. Per AGENTS.md it is built from the Linux CI artifacts: the firstv3.3tag run stops at "Verify all four retained packages", then the snapshot is built from that run's four artifacts, merged, and the tag is moved to the new commit.Test plan
npm run check:sync(v20, v21, v22 match v19)npm run test:scriptson Node 24.22.1 (all pass)--code-coverageand the four-line build (CI)🤖 Generated with Claude Code