Daz DeBoer f4925085d0 Consolidate short-lived token handling and resolve cache token via state ...

Have setupToken take the DevelocityConfig and return the short-lived JWT
matching the configured Develocity server, replacing resolveAccessKeyForServer
with resolveTokenForServer. Call setupToken directly from setup-gradle's
setup() (split out of buildScan.setup), persist the resolved token via
core.saveState, and read it back in complete(). cacheOptionsFrom now takes
the server URL and access token as parameters.

This ensures CacheOptions.develocityAccessToken is always the resolved
short-lived JWT on both restore and save, regardless of whether the access
key was supplied as an action input or env var.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-14 22:24:47 -06:00

..

init-scripts

Bump references to Develocity Gradle plugin from 4.4.0 to 4.4.2 (#973)

2026-06-09 12:25:09 -06:00

jest

Consolidate short-lived token handling and resolve cache token via state

2026-06-14 22:24:47 -06:00