Repository navigation
chore(release): 5.0.2-3 - #30
Merged
Merged
Conversation
haydenhoang
marked this pull request as ready for review
October 13, 2026 14:23
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
Prepare
5.0.2-3for the search input focus fix in #29, following the fixed versioning used by #28. Bump all seven packages and their internal dependencies, update the runtime version, add changelog entries, and regeneratebun.lock.Merge #29 before this PR. This branch contains release metadata only; publishing the focus fix requires both PRs on
main.Result
bun run build.bun run test:types.bun run test --run(297 tests across 40 files).git diff --checkpassed.5.0.2-3.Local validation used Node 24.20.0 and Bun 1.4.2. CI uses the pinned versions in
.tool-versions.After both PRs merge and CI passes, build the merged
mainand publish withbun run release --tag next. The current npmnextversion is5.0.2-2;latestremains on v3. The repository currently has CI for build/typecheck/tests, with no automated publish workflow.