[GH] (texera/aws-eks/01-template-reorg): Workflow run "Release Auditing" failed!

[GitBox <gi...@apache.org>]

The GitHub Actions job "Release Auditing" on texera.git/aws-eks/01-template-reorg has failed.
Run started by GitHub user aicam (triggered by aicam).

Head commit for run:
a1fcbabd6e2d92b6d74346fc9a07aae0915d0718 / ali <al...@gmail.com>
refactor(k8s): organize Helm templates into common/aws/onprem

Group the chart's templates by where they apply so the layout makes the
deployment surface obvious at a glance:

  templates/common/  resources every deployment needs (services, gateway,
                     postgres/lakefs/lakekeeper, computing-unit pool, RBAC)
  templates/onprem/  self-hosted-only resources (in-cluster MinIO)
  templates/aws/     AWS/EKS-only resources (added in later PRs; placeholder)

Helm renders templates/** recursively, so this is purely organizational:
`helm template` output is byte-identical to before the move (verified, modulo
the chart's pre-existing per-render random LakeFS keys). A templates/README.md
documents the convention and a .helmignore keeps the doc and .gitkeep
placeholder from being loaded as manifests.

Also bring values-development.yaml back in line with values.yaml (the ground
truth), which had drifted:
  - image source: docker.io/apache + 1.3.0-incubating-SNAPSHOT (was the stale
    ghcr.io/apache + latest), so both value files pull from the same place;
  - add the AUTH_JWT_SECRET entry to texeraEnvVars. values.yaml has it but the
    dev profile omitted it, so the computing-unit manager started without the
    secret and k8s computing-unit creation crashed with NoSuchElementException
    (None.get) in ComputingUnitManagingResource. Adding it (same dev-only
    default as values.yaml) makes CU creation work under the dev profile.

No behavior change to the default (on-prem) install.

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

Report URL: https://github.com/apache/texera/actions/runs/27705483987

With regards,
GitHub Actions via GitBox