Sync environments catalog with fission/environments dependency updates

[sanketsudake]

Summary

Syncs the site with the dependency-update series just merged into fission/environments master (PRs #436-#446), following the updating-environments-and-examples skill.

The site's static/data/environments.json stores only image/builder names (not runtime versions), so the only catalog deltas are the two environments whose image names were renamed:

• Go: go-env-1.23 / go-builder-1.23 -> go-env-1.26 / go-builder-1.26
• JVM-Jersey: jvm-jersey-env-22 / jvm-jersey-builder-22 -> jvm-jersey-env-25 / jvm-jersey-builder-25

Every other environment in the series changed only its runtime/version (Java 25, Python 3.13, Node 22.22.3, PHP 8.3, Ruby 3.4, Perl 5.42, TensorFlow Serving 2.20.0, binary alpine 3.22), with no image-name change, so their image arrays are byte-for-byte unchanged.

Upstream changes mirrored

Environment	Upstream change
jvm	Java 25 LTS / Spring Boot 3.5.14, jvm-env 1.32.0
jvm-jersey	images renamed -22 -> -25, 1.32.0
python	3.13 / Flask 3.1.3, 1.35.0
python-fastapi	3.13 / FastAPI 0.136.3, 1.35.0
nodejs	node 22.22.3, all three images 1.34
go	Go 1.26, go-env-1.25 -> go-env-1.26, 1.34.0
binary	alpine 3.22, 1.33.0
ruby	Ruby 3.4 (from EOL 2.6.1), 1.32.0
php	PHP 8.3 (from EOL 7.3), 1.32.0
perl	pinned perl 5.42, 1.32.0
tensorflow-serving	pinned 2.20.0, 1.32.0

dotnet (1.1) and dotnet20 (2.0) intentionally untouched upstream (EOL legacy; dotnet8 is the supported path).

Files changed

• static/data/environments.json - Go and JVM-Jersey image-name bumps.
• content/en/docs/usage/languages/go.md - bump go-env-1.23 examples + Go image table to 1.26.
• content/en/docs/usage/languages/_index.md - bump versioned Go env-create example to 1.26.
• content/en/docs/usage/triggers/message-queue-trigger-kind-keda/{kafka,redis,rabbitmq,nats-streaming,nats-jetstream}.md - bump versioned Go env-create examples to 1.26.

Historical release-notes pages (releases/1.4.1, 1.8.0, 1.9.0) that reference old go-env-1.12/1.13/1.14 were left as-is (they document past releases).

Notes / left for human review (not guessed)

• dotnet8 is not in the site catalog. Upstream environments.json now contains a dotnet8-env / dotnet8-builder entry (the supported .NET path), but static/data/environments.json has no card for it and tools/environments.py's env_dict has no mapping for Dotnet 8 Environment. Adding it is a new-environment content decision (card + logo + env_dict entry), out of scope for this version sync.
• tools/environments.py can't be run as-is. (1) It crashes with KeyError: 'Dotnet 8 Environment' on the current upstream manifest. (2) Upstream now uses name: "JVM Environment" for both jvm and jvm-jersey, so the script's name-based mapping would collapse both under "Java" and leave the dead env_dict key 'JVM Jersey Environment' unused. Because of these tooling gaps I applied the (mechanical, script-equivalent) image-name deltas by hand and verified them by grouping the upstream manifest by repo. The script should be fixed separately (key by repo, add dotnet8).
• content/en/docs/usage/languages/java.md line 8 still says the JVM environment "is based on openjdk8" - long-stale prose predating many JVM bumps (now Java 25). Left for a human since it is a content claim, not an image reference.

Verification

static/data/environments.json validates as JSON. Local ./build.sh fails only at the PostCSS/autoprefixer CSS transform due to a Node filesystem-permission sandbox quirk on this machine (browserslist walking outside the project dir) - unrelated to these changes, which touch only JSON data and Markdown. Relying on Netlify CI for the full build.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for fission-website ready!

Name	Link
🔨 Latest commit	8b8bc4f
🔍 Latest deploy log	https://app.netlify.com/projects/fission-website/deploys/6a244f09c9123700088819e7
😎 Deploy Preview	https://deploy-preview-292--fission-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sanketsudake]

Addressed the three review issues (commit 8b8bc4f).

Issue 1 — tools/environments.py crash & ambiguous mapping

Reworked the mapping to key by the upstream runtime image name instead of the display name.
The name field is no longer unique (both jvm-env and jvm-jersey-env-25 report "JVM Environment"), and the old code crashed with KeyError: 'Dotnet 8 Environment'.
Image names are unique, stable, and match the GHCR package names, so they map cleanly to the site catalog entries (Java vs Java (JVM-Jersey), etc.).
Unmapped upstream images now fail with a clear message instead of a KeyError.
The script runs cleanly end-to-end against the current upstream manifest and is idempotent (verified by running it three times — no spurious diffs).

Issue 2 — add .NET 8 to the site catalog

Added a .NET 8 entry to static/data/environments.json pointing at https://github.com/fission/environments/tree/master/dotnet8, with images dotnet8-env + dotnet8-builder.
The image array was generated by the fixed script (added a dotnet8-env -> .NET 8 mapping), so the catalog and the generator agree.
Reused the existing dotnetcore-logo.svg (no dedicated dotnet8 logo exists).

Issue 3 — stale prose in content/en/docs/usage/languages/java.md

Updated the intro: the JVM environment now runs on Java 25 (LTS, eclipse-temurin) with Spring Boot 3.5.x, not openjdk8, and noted the jvm-jersey variant (Jersey on Java 25).
Also bumped the illustrative spring-boot-starter-web example version from 2.0.1.RELEASE to 3.5.0 for consistency.
A repo-wide scan for other stale Java/Jersey version claims (openjdk, Java 8/11/22) outside release notes found no other occurrences.

Verification

• Both JSON files pass python -m json.tool.
• tools/environments.py runs cleanly and idempotently; scratch tools/environments.json deleted (not tracked).
• hugo page rendering succeeds; the full build only fails at the PostCSS/autoprefixer step due to the known sandbox FileSystemRead permission quirk (not a content issue).

🤖 Generated with Claude Code