What changes for you in FosterStack Cache v0.3.0

If you run FosterStack Cache for Gradle or Maven builds, these are the things to check before you upgrade from 0.2.2.

DRAFT for v0.3.0, not published and never merged before v0.3.0 is live. [TO-VERIFY] marks anything not yet checked against the release itself.

Check these before you upgrade

• Linux only. [TO-VERIFY] v0.3.0 ships Linux archives (amd64 and arm64) and no macOS archive. If you run the server on a Mac, run the container image or a Linux machine instead.
• No -debug image. [TO-VERIFY] The images are production and fips. To look inside a running container, use kubectl debug or docker debug.
• Oversized requests. [TO-VERIFY] A request with more than 500 header values is rejected with 431 before it reaches the cache. Gradle and Maven send far fewer.

What stays the same

[TO-VERIFY] The Gradle and Maven protocols, the FSCACHE_* settings and the data folder. No change is intended; confirm each against the release notes before this page says so.

How the release is built

[TO-VERIFY] Each stage of the release is signed on its own, and the signatures are verified together at release. The image is built from signed packages, with no base image. You can check all of it yourself: see verify a release yourself.

Upgrading

[TO-VERIFY] Whether the back-up and upgrade steps on the upgrade page change for this release. Support terms for v0.3.0: [TO-VERIFY].

Related: changelog and security policy.