chore: version packages#478
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
uploads-auth | d59fe96 | Commit Preview URL Branch Preview URL |
Jul 23 2026, 06:20 PM |
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.27.0
Minor Changes
ee057cc:
meta setrefreshes the managed PR/issue comment when it changespathorstateon agh/…-keyed attachment, so backfilled metadata shows up without waiting for the next attach. If the bot endpoint is unavailable it prints auploads commenthint instead of failing the write. The server side also self-heals duplicate managed comments left by a create race: the oldest is kept and updated, extras are deleted on the next sync (issue Managed comment: create race duplicates the bot comment; no re-sync after meta set #470).5fbf612:
uploads screenshot(CLI and local MCP) now stages against the current git branch by default when run on a non-default branch with no--pr/--issue/--branchtarget — same key and metadata asattach --branch, so derived facts (path/url/env/viewport, plus--state) survive through to the PR once it opens instead of being lost at attach time. Opt out with--no-git, or an explicit--ref/--prefix/--destination.attachandput --pr/put --issuenow print atip: add --meta path=/route so this shot is findable by page(stderr, plus a JSONhintfield) when an uploaded image ends up with nopathmetadata. Respects--quiet.5d29337:
uploads screenshot --outnow also writes a sidecar manifest (<file>.uploads.json) recording the capture's derived metadata (path/url/env/viewport, plus--stateif given) with a content hash. A lateruploads put/attachof that exact file automatically picks the metadata back up — explicit--meta/--statestill win, and a regenerated or edited file silently loses its sidecar. Disable with--no-sidecar.Patch Changes
meta setcomment re-sync (path/state) added in fix(api,cli): self-heal duplicate managed comments; re-sync after meta set #471, in the CLI README, the
uploads-cli skill, and the GitHub App docs page.