Repository navigation
chore(release): prepare Retree 0.11.2 - #131
Merged
Merged
Conversation
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.
Prepares Retree 0.11.2 from the eight merged patch changesets. Uses the repository's
version:packagesworkflow to consume those changesets, generate changelog entries, and update all eight lockstep package versions, exact internal dependency pins, and the lockfile. The benchmark CLI's runtime dependency pins also move to 0.11.2; the independently versioned React ESLint plugin stays at 0.1.1.The release includes:
DOMExceptionandURL, work as tree leaves.Retree.untracked.clearListenersavoids duplicate teardown.Consumer notes are included in the generated changelogs: ReactiveNode teardown from React hooks is deferred by one microtask, so fake-timer tests need to flush it. Custom query reconcilers should use
reconcileArrayor return a replacement rather than assigning objects fromnextdirectly intocurrent.Local validation passed:
npm run test: 125 files, 1,751 tests.npm run typecheck.npm run doctorandnpm run lint:architecture.npm run lint:packages, including package builds, publint, attw, and Node import smoke tests.git diff --check, and release-notes dry run.After merging, run the manual
Releaseworkflow onmainto publish the packages and create the tag and GitHub release.