Skip to content
cccskills
FreePublished on GitHub

fastly-compute-rust-edition2024-fix

Fix Fastly Compute Rust build failures caused by edition2024 dependencies. Use when: (1) cargo build fails with "feature `edition2024` is required", (2) wit-bindgen or wasip2 crates fail to download/parse, (3) Fastly SDK pulls in incompatible transitive dependencies, (4) Build worked before but fails after dependency update. Solves by pinning wit-bindgen, wasip2, and related crates to pre-edition2024 versions.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Fastly Compute Rust Edition2024 Dependency Fix

Problem

Fastly Compute Rust projects fail to build with errors about edition2024 being required, even when using stable Rust. The error appears when transitive dependencies (especially wit-bindgen 0.51+ and wasip2 1.0.2+) require Rust 1.87+ which isn't stable yet.

Context / Trigger Conditions

  • Error: feature 'edition2024' is required
  • Error: failed to parse manifest at .../wit-bindgen-0.51.0/Cargo.toml
  • Error mentions "requires Rust 1.87.0" for wit-bindgen or wasip2
  • Build previously worked but fails after running cargo update
  • Using Fastly SDK (fastly crate) version 0.11.x

Solution

Pin the problematic transitive dependencies in your Cargo.toml:

[dependencies]
# Fastly Compute SDK - pin to specific version
fastly = "=0.11.12"

# Pin these to avoid edition2024 requirement
wit-bindgen = "=0.46.0"
wasip2 = "=1.0.1"

# Also pin these if you use k256 or crypto
k256 = { version = "=0.13.3", features = ["schnorr"] }
base64ct = "=1.6.0"

Also update rust-toolchain.toml to include both WASM targets:

[toolchain]
channel = "1.83.0"
targets = ["wasm32-wasi", "wasm32-wasip1"]

Then:

rm Cargo.lock
rustup target add wasm32-wasip1
cargo build --target wasm32-wasi

Verification

Build should complete without edition2024 errors:

cargo build --target wasm32-wasi 2>&1 | grep -i "edition2024"
# Should return nothing (no matches)

Example

Before fix (Cargo.toml):

[dependencies]
fastly = "0.11"  # Allows 0.11.x which pulls wit-bindgen 0.51+

After fix (Cargo.toml):

[dependencies]
fastly = "=0.11.12"
wit-bindgen = "=0.46.0"
wasip2 = "=1.0.1"

Notes

  • The = prefix in version strings means "exactly this version"
  • Fastly CLI 13.x switched from wasm32-wasi to wasm32-wasip1 target
  • This is a temporary fix until Rust 1.87 becomes stable
  • The warning about wasm32-wasi being renamed to wasm32-wasip1 is expected
  • When Rust 1.87 is stable, these pins can be removed

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

See all skills by divinevideo

Report a problem with this skill