Repository navigation
chore: release - #58
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 17, 2026 20:48
0c95e3c to
35e5e2c
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@nsxbet/jest-orchestrator@0.2.1
Patch Changes
#55
14d5160Thanks @gtkatakura! - Use 10-second fallback estimates and same-file/global timing fallbacks for Jest shard plans, and report selected skipped tests accurately.#59
a4d80afThanks @gtkatakura! - Format human-facing durations consistently as milliseconds, seconds, or composed minute/hour units, and improve E2E lifecycle summary tables.@nsxbet/playwright-orchestrator@2.0.1
Patch Changes
#59
a4d80afThanks @gtkatakura! - Handle valid empty shard plans as no-ops and exclude skipped tests from timing measurements so exact test assignments remain intact.#59
a4d80afThanks @gtkatakura! - Format human-facing durations consistently as milliseconds, seconds, or composed minute/hour units, and improve E2E lifecycle summary tables.