Repository navigation
chore: version packages (alpha) - #159
Merged
Merged
Conversation
|
Note The title starts with
|
devnacho
force-pushed
the
changeset-release/main
branch
from
October 20, 2026 01:39
c695ac1 to
02c093f
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 20, 2026 12:06
02c093f to
2a4c1e5
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 20, 2026 22:40
2a4c1e5 to
d04b23b
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 21, 2026 00:12
d04b23b to
d5bb825
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 23, 2026 00:14
d5bb825 to
a9ad666
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 23, 2026 00:42
a9ad666 to
73a9012
Compare
devnacho
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 23, 2026 15:17
239027f to
2849e58
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 23, 2026 15:50
2849e58 to
a9bca57
Compare
devnacho
force-pushed
the
changeset-release/main
branch
from
October 23, 2026 16:19
a9bca57 to
324e79b
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.19
Minor Changes
--no-cloud, and retry transient delivery failures within a bounded budget.SEDUM_BROWSER(process orproject
.env) and a named environment'sbrowserkey now set the browser,below
--browserand above the top-levelbrowserkey.sedum doctoraccepts--browserand reports where the browser setting came from.Patch Changes
wait until …step before them. A target that a render pass replaces while it is being located is located again, on busy pages too, until the page holds still. A click that Playwright refused before sending any input is retried against the new target. A step whose target never holds still now fails instead of "could not run", so--retriesreruns it. A located button that stays disabled, or a field that stays read-only, now waits for the step timeout when that is longer than 8 seconds, and a quoted-text check keeps reading a page that is mid-navigation. Set the step timeout withstepTimeoutMsinsedum.config.yaml, per environment if needed.@sedum-dev/core@0.1.0-alpha.19
Patch Changes
or route, even if the new page is still loading or changing. Such an action
used to end with
action_uncertain(the test could not run, with no retry)when the next page took more than about 4 seconds to load, as a cross-app page
on a busy machine does. Later steps wait for the page as before; the action is
still never replayed, and an unreadable new document is still uncertain.
--retriesreruns the test. Provider failures that affect the whole run, such as a rejected API key, a configuration error or a rate limit, still stop the run as before.wait until …step before them. A target that a render pass replaces while it is being located is located again, on busy pages too, until the page holds still. A click that Playwright refused before sending any input is retried against the new target. A step whose target never holds still now fails instead of "could not run", so--retriesreruns it. A located button that stays disabled, or a field that stays read-only, now waits for the step timeout when that is longer than 8 seconds, and a quoted-text check keeps reading a page that is mid-navigation. Set the step timeout withstepTimeoutMsinsedum.config.yaml, per environment if needed.text_unreadableinstead of "could not run", so--retriesreruns the test.@sedum-dev/provider-clef@0.1.0-alpha.19
Patch Changes
@sedum-dev/provider-typesafe@0.1.0-alpha.19
Patch Changes
@sedum-dev/reporters@0.1.0-alpha.19
Patch Changes