Repository navigation
Tags: PGCodeLLM/act
Tags
feat: apply configurable RUNNER_TEMP to runner.temp context too Keeps the runner.temp expression context consistent with the RUNNER_TEMP env var, so workflows reading both (e.g. gh-aw) see the same directory.
artifacts(v4): accept actions/upload-artifact@v7 (tolerant decode + u…
…npadded SAS sig)
Two fixes in pkg/artifacts/artifacts_v4.go so act's bundled artifact-V4 server
interoperates with actions/upload-artifact@v7 (the version gh-aw pins):
- parseProtbufBody: protojson.UnmarshalOptions{DiscardUnknown:true} — the v7
client sends a `mime_type` field absent from the bundled CreateArtifactRequest
proto; strict decoding returned HTTP 500 with an empty body (client: "Unexpected
end of JSON input").
- buildArtifactURL/verifySignature: base64.RawURLEncoding (unpadded) for the SAS
sig — the v7 Azure-blob client strips trailing '=' padding from query params, so
a padded sig failed to decode on verify ("Error unauthorized").
Adds handler-level tests (artifacts_v4_compat_test.go) covering both; verified
they fail without the fixes.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
feat: make RUNNER_TEMP configurable via Config.RunnerTemp
PreviousNext