chore: version packages - #718
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
uploads-auth | e79838f | Commit Preview URL Branch Preview URL |
Aug 20 2026, 07:35 PM |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 20, 2026 19:34
df2560c to
e79838f
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
1 participant
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.
Releases
@buildinternet/uploads@0.46.0
Minor Changes
screenshotgains--wait-for <js>(local backend), a hydration-aware gate that polls a JS expression in the page until truthy before--evaland capture (issue screenshot --eval: clicks fire before React hydration — add a post-hydration/interaction hook #715). Theload/networkidlesettle strategies fire before a React/Next app hydrates, so a syntheticel.click()in--evalhit the still-inert server-rendered DOM with no handler attached — silently doing nothing. Expressing the app's own "interactive" signal (e.g.--wait-for 'window.__hydrated===true') closes that gap; a predicate that never becomes truthy fails withRENDER_FAILEDinstead of capturing the un-ready page.--wait-foris local-only (rejected up front on--via remote, like--eval).--eval/--wait-forhelp and the CLI docs now warn that synthetic events won't reach framework handlers until hydration.