From d59fe9667d2f74eb4af56410c28be58ec6713e4d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 23 Jul 2026 18:19:22 +0000 Subject: [PATCH] chore: version packages --- .changeset/docs-471-comment-resync-followup.md | 7 ------- .../duplicate-comment-dedupe-meta-resync.md | 5 ----- .changeset/screenshot-branch-staging.md | 7 ------- .changeset/screenshot-sidecar-metadata.md | 5 ----- packages/uploads/CHANGELOG.md | 17 +++++++++++++++++ packages/uploads/package.json | 2 +- 6 files changed, 18 insertions(+), 25 deletions(-) delete mode 100644 .changeset/docs-471-comment-resync-followup.md delete mode 100644 .changeset/duplicate-comment-dedupe-meta-resync.md delete mode 100644 .changeset/screenshot-branch-staging.md delete mode 100644 .changeset/screenshot-sidecar-metadata.md diff --git a/.changeset/docs-471-comment-resync-followup.md b/.changeset/docs-471-comment-resync-followup.md deleted file mode 100644 index cb46bfcd..00000000 --- a/.changeset/docs-471-comment-resync-followup.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@buildinternet/uploads": patch ---- - -Docs: document the managed-comment self-heal dedupe and the `meta set` -comment re-sync (path/state) added in #471, in the CLI README, the -uploads-cli skill, and the GitHub App docs page. diff --git a/.changeset/duplicate-comment-dedupe-meta-resync.md b/.changeset/duplicate-comment-dedupe-meta-resync.md deleted file mode 100644 index 6257623f..00000000 --- a/.changeset/duplicate-comment-dedupe-meta-resync.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@buildinternet/uploads": minor ---- - -`meta set` refreshes the managed PR/issue comment when it changes `path` or `state` on a `gh/…`-keyed attachment, so backfilled metadata shows up without waiting for the next attach. If the bot endpoint is unavailable it prints a `uploads comment` hint 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 #470). diff --git a/.changeset/screenshot-branch-staging.md b/.changeset/screenshot-branch-staging.md deleted file mode 100644 index 6c935fd8..00000000 --- a/.changeset/screenshot-branch-staging.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@buildinternet/uploads": minor ---- - -`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`/`--branch` target — same key and metadata as `attach --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`. - -`attach` and `put --pr`/`put --issue` now print a `tip: add --meta path=/route so this shot is findable by page` (stderr, plus a JSON `hint` field) when an uploaded image ends up with no `path` metadata. Respects `--quiet`. diff --git a/.changeset/screenshot-sidecar-metadata.md b/.changeset/screenshot-sidecar-metadata.md deleted file mode 100644 index 824633dd..00000000 --- a/.changeset/screenshot-sidecar-metadata.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@buildinternet/uploads": minor ---- - -`uploads screenshot --out` now also writes a sidecar manifest (`.uploads.json`) recording the capture's derived metadata (path/url/env/viewport, plus `--state` if given) with a content hash. A later `uploads put`/`attach` of that exact file automatically picks the metadata back up — explicit `--meta`/`--state` still win, and a regenerated or edited file silently loses its sidecar. Disable with `--no-sidecar`. diff --git a/packages/uploads/CHANGELOG.md b/packages/uploads/CHANGELOG.md index b1d3d880..fa8904ef 100644 --- a/packages/uploads/CHANGELOG.md +++ b/packages/uploads/CHANGELOG.md @@ -1,5 +1,22 @@ # @buildinternet/uploads +## 0.27.0 + +### Minor Changes + +- ee057cc: `meta set` refreshes the managed PR/issue comment when it changes `path` or `state` on a `gh/…`-keyed attachment, so backfilled metadata shows up without waiting for the next attach. If the bot endpoint is unavailable it prints a `uploads comment` hint 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 #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`/`--branch` target — same key and metadata as `attach --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`. + + `attach` and `put --pr`/`put --issue` now print a `tip: add --meta path=/route so this shot is findable by page` (stderr, plus a JSON `hint` field) when an uploaded image ends up with no `path` metadata. Respects `--quiet`. + +- 5d29337: `uploads screenshot --out` now also writes a sidecar manifest (`.uploads.json`) recording the capture's derived metadata (path/url/env/viewport, plus `--state` if given) with a content hash. A later `uploads put`/`attach` of that exact file automatically picks the metadata back up — explicit `--meta`/`--state` still win, and a regenerated or edited file silently loses its sidecar. Disable with `--no-sidecar`. + +### Patch Changes + +- 14edc6f: Docs: document the managed-comment self-heal dedupe and the `meta set` + comment re-sync (path/state) added in #471, in the CLI README, the + uploads-cli skill, and the GitHub App docs page. + ## 0.26.1 ### Patch Changes diff --git a/packages/uploads/package.json b/packages/uploads/package.json index ae9bdc3e..919890c5 100644 --- a/packages/uploads/package.json +++ b/packages/uploads/package.json @@ -1,6 +1,6 @@ { "name": "@buildinternet/uploads", - "version": "0.26.1", + "version": "0.27.0", "description": "CLI and client for uploads.sh — workspace-scoped image hosting for GitHub embeds", "type": "module", "sideEffects": false,