Repository navigation
chore: version packages (alpha) - #178
Merged
Merged
Conversation
devnacho
force-pushed
the
changeset-release/main
branch
from
October 26, 2026 23:13
2b0f478 to
46d6bda
Compare
|
Note The title starts with
|
devnacho
force-pushed
the
changeset-release/main
branch
from
October 26, 2026 23:14
46d6bda to
b4e1c63
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 26, 2026 23:14
b4e1c63 to
7f2110d
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 27, 2026 01:20
7f2110d to
e611b00
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 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.20
Patch Changes
| true,| head, or a failingjq, instead of crashing with an unhandledEPIPE. The authentication store lock is now released on any exit, and a lock left by a killed process on the same host and PID namespace is detected and cleared automatically. A lock held by a live or paused process still blocks, so concurrent refresh-token rotation stays serialized.sedum runnow prints the Cloud run UUID thatsedum runs showaccepts, next to the local run ID. Upload warnings name the likely cause: an unset or malformedSEDUM_UPLOAD_TOKEN,SEDUM_PROJECT_IDorSEDUM_CLOUD_URL, missing Git context, an unreachable host, or an HTTP 401 for a token that is revoked or issued for another project.runs showwith a local run ID now says the run was not found instead of reporting a membership problem. Uploads still never change the exit code.npm install -D sedum-clireported 6 high-severity vulnerabilities innpm audit. It now reports none.@sedum-dev/core@0.1.0-alpha.20
Patch Changes
close while the page reloads and then keep the tab open, and the run waited for
it forever: it wrote no
result.json, stayedrunninginprogress.json, andignored Ctrl-C. Sedum now stops waiting after 2 seconds and closes the page's
browser context, which always disposes it, so retries, Ctrl-C and
--timeout-minutesreport their results again.stepTimeoutMswhen that is longer than 4 seconds, instead of always giving up after 4 seconds. A page that never holds still now fails the step withobservation_timeoutinstead of "could not run", so--retriesreruns the test.npm install -D sedum-clireported 6 high-severity vulnerabilities innpm audit. It now reports none.@sedum-dev/provider-clef@0.1.0-alpha.20
Patch Changes
@sedum-dev/provider-typesafe@0.1.0-alpha.20
Patch Changes
@sedum-dev/reporters@0.1.0-alpha.20
Patch Changes