Repository navigation
chore: version packages (alpha) - #180
Merged
Merged
Conversation
|
Note The title starts with
|
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 publish to npm yourself or setup this action to publish 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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
sedum-cli@0.1.0-alpha.21
Minor Changes
sedum run --non-blocking-labels <tags>to quarantine flaky tests without skipping them. Tests with any of the tags run and are reported as usual, but their failures and test-scoped errors do not fail the run or the exit code.result.jsonmarks them"blocking": falseand counts their failures intotals.nonBlockingFailedTests;totals.failedTestsnow counts blocking failures only. The terminal summary, the Markdown and HTML reports, and JUnit show non-blocking failures separately. JUnit records them as skipped.Patch Changes
@sedum-dev/core@0.1.0-alpha.21
Minor Changes
sedum run --non-blocking-labels <tags>to quarantine flaky tests without skipping them. Tests with any of the tags run and are reported as usual, but their failures and test-scoped errors do not fail the run or the exit code.result.jsonmarks them"blocking": falseand counts their failures intotals.nonBlockingFailedTests;totals.failedTestsnow counts blocking failures only. The terminal summary, the Markdown and HTML reports, and JUnit show non-blocking failures separately. JUnit records them as skipped.@sedum-dev/reporters@0.1.0-alpha.21
Minor Changes
sedum run --non-blocking-labels <tags>to quarantine flaky tests without skipping them. Tests with any of the tags run and are reported as usual, but their failures and test-scoped errors do not fail the run or the exit code.result.jsonmarks them"blocking": falseand counts their failures intotals.nonBlockingFailedTests;totals.failedTestsnow counts blocking failures only. The terminal summary, the Markdown and HTML reports, and JUnit show non-blocking failures separately. JUnit records them as skipped.Patch Changes
@sedum-dev/provider-clef@0.1.0-alpha.21
Patch Changes
@sedum-dev/provider-typesafe@0.1.0-alpha.21
Patch Changes