Repository navigation
Version Packages - #655
Version Packages#655
Conversation
|
The generated release head hit a concrete fixture dependency bug: |
363d94e to
3b8276d
Compare
|
Release completed: all 14 executed checks passed on 3b8276d; squash merge 99d00a8 triggered successful publication run https://github.com/transloadit/node-sdk/actions/runs/43526593429. Node/legacy CLI 6.9.0, Utils 4.11.0 and MCP-server 0.8.8 are independently visible with their expected latest tags and GitHub releases. The MCP Registry also reports active 0.8.8 (not an API2 hosted-MCP deploy). A fresh consumer installed the published Node/Utils packages and passed Storage export/URL and CLI checks without API calls. Initial registry absence and ETARGET were retained; visibility was awaited without republication. API2 adoption and the earlier 34 real Storage/CDN acceptance checks remain recorded in the canonical DAM-067 evidence: https://github.com/transloadit/team-internals/blob/main/projects/dam/evidence/2026-11-13-storage-acceptance.md |
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
@transloadit/node@6.9.0
Minor Changes
af611d4: Store mixed-media originals with
storeAsset()and recover verified receipts without uploading.The Storage CLI checkpoints both image and file receipts in one catalog, skips matching replays,
and stops with recoverable evidence if the server changes original bytes. Viewer remains image-only.
Add
getPublicStoredAssetUrl()for version-pinned originals, downloads and bounded still previews.Its new Built-ins require the corresponding API2 deployment before adoption; URL construction
does not publish assets. Existing
storeImage()behavior is preserved.The generic CLI intentionally now requires unchanged original bytes, including for images: a
server-transformed upload exits nonzero after saving its actual receipt instead of silently
accepting a watermark. It uses the
fileupload field. Use the existing SDKstoreImage()APIwhen deliberately accepting transformed image bytes.
Plain and hashed replays both trust the local receipt's byte hash and do not verify live existence.
Refresh stale catalogs with
storage receipts sync; incomplete legacy receipts require recoverybefore replay. Sync cannot generate a missing checksum. Dimensionless files and unknown MIME types
remain in
filesoutside Viewer's typed map; new uploads and sync require an explicit image MIMEtype to classify an entry as a Viewer image. Existing catalogs remain readable.
Patch Changes
transloadit@6.9.0
Minor Changes
af611d4: Store mixed-media originals with
storeAsset()and recover verified receipts without uploading.The Storage CLI checkpoints both image and file receipts in one catalog, skips matching replays,
and stops with recoverable evidence if the server changes original bytes. Viewer remains image-only.
Add
getPublicStoredAssetUrl()for version-pinned originals, downloads and bounded still previews.Its new Built-ins require the corresponding API2 deployment before adoption; URL construction
does not publish assets. Existing
storeImage()behavior is preserved.The generic CLI intentionally now requires unchanged original bytes, including for images: a
server-transformed upload exits nonzero after saving its actual receipt instead of silently
accepting a watermark. It uses the
fileupload field. Use the existing SDKstoreImage()APIwhen deliberately accepting transformed image bytes.
Plain and hashed replays both trust the local receipt's byte hash and do not verify live existence.
Refresh stale catalogs with
storage receipts sync; incomplete legacy receipts require recoverybefore replay. Sync cannot generate a missing checksum. Dimensionless files and unknown MIME types
remain in
filesoutside Viewer's typed map; new uploads and sync require an explicit image MIMEtype to classify an entry as a Viewer image. Existing catalogs remain readable.
Patch Changes
@transloadit/utils@4.11.0
Minor Changes
af611d4: Store mixed-media originals with
storeAsset()and recover verified receipts without uploading.The Storage CLI checkpoints both image and file receipts in one catalog, skips matching replays,
and stops with recoverable evidence if the server changes original bytes. Viewer remains image-only.
Add
getPublicStoredAssetUrl()for version-pinned originals, downloads and bounded still previews.Its new Built-ins require the corresponding API2 deployment before adoption; URL construction
does not publish assets. Existing
storeImage()behavior is preserved.The generic CLI intentionally now requires unchanged original bytes, including for images: a
server-transformed upload exits nonzero after saving its actual receipt instead of silently
accepting a watermark. It uses the
fileupload field. Use the existing SDKstoreImage()APIwhen deliberately accepting transformed image bytes.
Plain and hashed replays both trust the local receipt's byte hash and do not verify live existence.
Refresh stale catalogs with
storage receipts sync; incomplete legacy receipts require recoverybefore replay. Sync cannot generate a missing checksum. Dimensionless files and unknown MIME types
remain in
filesoutside Viewer's typed map; new uploads and sync require an explicit image MIMEtype to classify an entry as a Viewer image. Existing catalogs remain readable.
@transloadit/mcp-server@0.8.8
Patch Changes
af611d4: Store mixed-media originals with
storeAsset()and recover verified receipts without uploading.The Storage CLI checkpoints both image and file receipts in one catalog, skips matching replays,
and stops with recoverable evidence if the server changes original bytes. Viewer remains image-only.
Add
getPublicStoredAssetUrl()for version-pinned originals, downloads and bounded still previews.Its new Built-ins require the corresponding API2 deployment before adoption; URL construction
does not publish assets. Existing
storeImage()behavior is preserved.The generic CLI intentionally now requires unchanged original bytes, including for images: a
server-transformed upload exits nonzero after saving its actual receipt instead of silently
accepting a watermark. It uses the
fileupload field. Use the existing SDKstoreImage()APIwhen deliberately accepting transformed image bytes.
Plain and hashed replays both trust the local receipt's byte hash and do not verify live existence.
Refresh stale catalogs with
storage receipts sync; incomplete legacy receipts require recoverybefore replay. Sync cannot generate a missing checksum. Dimensionless files and unknown MIME types
remain in
filesoutside Viewer's typed map; new uploads and sync require an explicit image MIMEtype to classify an entry as a Viewer image. Existing catalogs remain readable.
Updated dependencies [af611d4]
Release acceptance: API2 #11099 is deployed on the required uploader/worker fleet; the bounded four-asset Storage/CDN matrix passed all 34 HTTP checks. The original CI fixture failure is retained; #656 fixes pre-publication local Utils resolution, and this regenerated head includes that merged fix. No backend rollout is performed by this release.
🤖 Claimed by kvz on
framework1/node-sdksince 2026-11-13 · resume:codex resume 019fa2ee-f994-79d0-9d50-071bf2cb7ad6