chore(deps): update dependency @fastly/compute-js-static-publish to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@fastly/compute-js-static-publish	6.2.0 → 7.0.7

---

Release Notes

fastly/compute-js-static-publish (@​fastly/compute-js-static-publish)

v7.0.7

Compare Source

• Update to CLI v15

v7.0.6

Compare Source

Updated

• Release to npmjs using updated CI workflow

v7.0.5

Compare Source

Added

• Add application/wasm to default content types

v7.0.4

Compare Source

Added

• Publish to GitHub packages as well
• Use NPM trusted publishing for publishing to npmjs.com

v7.0.3

Compare Source

Fixed

• Use pathToFileURL so that import() works under ESM across platforms #​38

v7.0.2

Compare Source

Fixed

• Fix script listed in readme instructions
• Handle symlinks properly in file enumeration #​41

v7.0.1

Compare Source

Fixed

• Add @latest to examples of calling the app in scaffolding mode.

v7.0.0

Compare Source

[!NOTE]
Breaking release. Every project will need a re-scaffold.

Added

• Named Collections

  • Support for named collections of assets that are managed together and can be individually previewed.
  • Expiration trio: --expires-in, --expires-at, --expires-never.
  • Collection selector utilities that can be run at the edge code to activate a collection.
  • Default collection never expires.

• git-style subcommands

  • Actions separated into subcommands, such as clean, publish-content, and collections.
  • Dry-run mode (--dry-run) for commands that mutates KV or disk.

• KV Store

  • Bytes of assets are stored in the Fastly KV Store.
  • Items in the KV Store are keyed by the hash of the file, keeping storage efficient and deduplicated, even across collections.
  • Metadata (file sizes, encodings, compression) for static assets is stored in KV Store Item metadata.
  • Large-object chunking: files > 20 MB are split into segments behind the scenes and reassembled at read time.
  • Upload process has been optimized - files are uploaded in parallel, and are only compressed and uploaded when necessary.
  • Automatic retry with exponential back-off when the Fastly KV API rate-limits a burst of uploads.
  • Fully supported in the local development environment during development.
  • --local flag for all management commands. Passing this flag makes the command operate on the local KV Store instead of the Fastly KV Store.

Changed

• Separate config files:

  • static-publisher.rc.js now owns behavior that is common to the scaffolded Compute app
  • publish-time settings are in publish-content.config.js.

• Script names in the scaffold are now grouped by environment: dev:publish, dev:start, fastly:publish, fastly:deploy.

• Asset inclusion test renamed to kvStoreAssetInclusionTest and now expects a boolean return value.

Removed / Deprecated

• This tool drops wasm-inline, and no longer inlines bytes of assets into the Wasm binary.

• Static files metadata is no longer stored in the Wasm binary,

• This tool drops moduleAssets.

v6.3.0

Compare Source

Added

• feat: Added content type for WebP images
• Added example of adding a custom content type to README

Fixed

• fix: Content Type test regexes were not checking period correctly

Updated

• Uses new webpack recommendations from webpack starter kit
• Minor updates to migration guide

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @contentful/f36-cdn@1.0.0
npm ERR! Found: @fastly/js-compute@3.32.2
npm ERR! node_modules/@fastly/js-compute
npm ERR!   @fastly/js-compute@"3.32.2" from @contentful/f36-cdn@1.0.0
npm ERR!   packages/cdn
npm ERR!     @contentful/f36-cdn@1.0.0
npm ERR!     node_modules/@contentful/f36-cdn
npm ERR!       workspace packages/cdn from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @fastly/js-compute@"^3.33.2" from @fastly/compute-js-static-publish@7.0.7
npm ERR! node_modules/@fastly/compute-js-static-publish
npm ERR!   dev @fastly/compute-js-static-publish@"7.0.7" from @contentful/f36-cdn@1.0.0
npm ERR!   packages/cdn
npm ERR!     @contentful/f36-cdn@1.0.0
npm ERR!     node_modules/@contentful/f36-cdn
npm ERR!       workspace packages/cdn from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-16T14_19_27_660Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
forma-36	Error		Jul 15, 2026 4:12am
forma-36-storybook	Error		Jul 15, 2026 4:12am

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa8c447

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR