The release pipeline fails when enabling the GitHub feature "immutable releases". This is because the pipeline is modifying a release by uploading files after making the release public.
Here is an example: https://github.com/bazel-contrib/rules_img/actions/runs/19863610282/job/56921613192
Run softprops/action-gh-release@v1
with:
files: attestations/*
repository: bazel-contrib/rules_img
tag_name: v0.2.11
token: ***
env:
REGISTRY_BRANCH: main
REGISTRY: bazelbuild/bazel-central-registry
REGISTRY_FORK: bazel-contrib/bazel-central-registry
TAG_NAME: v0.2.11
VERSION: 0.2.11
⬆️ Uploading rules_img_pull_tool.MODULE.bazel.intoto.jsonl...
⬆️ Uploading rules_img_pull_tool.source.json.intoto.jsonl...
⬆️ Uploading rules_img_tool.MODULE.bazel.intoto.jsonl...
⬆️ Uploading rules_img_tool.source.json.intoto.jsonl...
⬆️ Uploading rules_img.MODULE.bazel.intoto.jsonl...
⬆️ Uploading rules_img.source.json.intoto.jsonl...
Error: Failed to upload release asset rules_img_pull_tool.MODULE.bazel.intoto.jsonl. received status code 422
Cannot upload assets to an immutable release.
undefined
The release pipeline fails when enabling the GitHub feature "immutable releases". This is because the pipeline is modifying a release by uploading files after making the release public.
Here is an example: https://github.com/bazel-contrib/rules_img/actions/runs/19863610282/job/56921613192