Skip to content

fix(ci): support immutable releases in chart release workflow - #364

Merged
SoulPancake merged 1 commit into
mainfrom
fix/release-immutable-releases
Oct 29, 2026
Merged

SoulPancake merged 1 commit into
mainfrom
fix/release-immutable-releases

Conversation

@SoulPancake

@SoulPancake SoulPancake commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Problem

The last two release runs failed (0.3.17, 0.3.18) with:

422 Cannot upload assets to an immutable release

Root cause: GitHub immutable releases were enabled for this repo between the 0.3.16 (Oct 6, immutable: false) and 0.3.17 (Oct 29, immutable: true) releases. chart-releaser v1.7.0 creates the release published-first, then uploads the .tgz — immutable releases reject any asset upload after publish. Result: openfga-0.3.17 and openfga-0.3.18 exist as published, empty releases (no chart assets), never reached index.yaml or GHCR. Not related to the runner image migration.

Fix

Both changes are intentionally in one PR: merging the version bump without the action bump would mint another empty immutable release; merging the action bump alone releases nothing (0.3.18 is skipped as existing).

Verification

Tested chart-releaser v1.9.0 upload end-to-end against a repository with immutable releases enabled — the release was published with the chart asset attached:

{"draft": false, "immutable": true,
 "assets": [{"name": "crtest-0.0.1-crtest.tgz", "size": 4922, "state": "uploaded"}]}

Also: helm lint clean, 34/34 unit tests pass, workflow YAML validated.

After merge

  • Release workflow publishes openfga-0.3.19 with assets, updates index.yaml, pushes to GHCR.
  • 0.3.17/0.3.18 remain as empty husk releases (cannot be deleted); suggest editing their release notes to point at 0.3.19.

Copilot AI balanced review requested due to automatic review settings October 29, 2026 15:51
@SoulPancake
SoulPancake requested review from a team as code owners October 29, 2026 15:51
@coderabbitai

coderabbitai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ace4d1b3-20f6-455f-9bc2-7b30cf37215b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c03767ec-1447-4c50-b201-c6e43b9ed508
Commits

Reviewing files that changed from the base of the PR and between c64e132 and c784ff9.

Files selected for processing: 2
  • .github/workflows/release.yml
  • charts/openfga/Chart.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The OpenFGA Helm chart version changes from 0.3.18 to 0.3.19. The release workflow updates its pinned chart-releaser action from v1.7.0 to v1.8.0.

Changes

Chart release

Layer / File(s) Summary
Release metadata and action
charts/openfga/Chart.yaml, .github/workflows/release.yml
The chart version changes to 0.3.19. The release workflow uses chart-releaser-action v1.8.0.

Priority: Pending latest changes

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Possibly related PRs

  • openfga/helm-charts#327: Adds minReadySeconds and deploymentStrategy values and templates that are described as shipping with chart version 0.3.19.

Suggested reviewers: siddhant-k-code, vic-dev

Merge Risk: Minimal · previous review c784f

The release metadata and action updates are consistent with the intended immutable-release fix and are ready to merge.

Pre-merge checks: Passed 4
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title names the main change: the chart release workflow is updated so immutable GitHub releases work. The raw summary lists only the chart-releaser-action bump and the chart version bump, and the …
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the main change: the chart release workflow is updated so immutable GitHub releases work. The raw summary lists only the chart-releaser-action bump and the chart version bump, and the objectives confirm that the action bump is the fix for immutable-release asset uploads. The title is specific and matches the changeset. The 'fix(ci)' prefix follows conventional commit style.

Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

GitHub immutable releases were enabled for this repo between the
openfga-0.3.16 (Oct 6) and openfga-0.3.17 (Oct 29) releases. The
chart-releaser v1.7.0 flow (create published release, then upload
assets) now fails with:

  422 Cannot upload assets to an immutable release

leaving openfga-0.3.17 and openfga-0.3.18 as published, immutable,
asset-less releases that never reached the helm repo index or GHCR.

Changes:
- Bump helm/chart-releaser-action to v1.8.0 (chart-releaser v1.9.0),
  which creates the release as a draft, uploads assets, and only then
  publishes (helm/chart-releaser#587), compatible with immutable
  releases. Verified end-to-end against a repository with immutable
  releases enabled: release published with assets attached.
- Bump chart to 0.3.19: the 0.3.17/0.3.18 releases and tags are
  immutable (tags cannot be deleted or moved) and CR_SKIP_EXISTING
  skips them, so a new version is required for the next release to
  ship. 0.3.19 carries the previously unreleased changes (OpenFGA
  v1.22.1, minReadySeconds/deploymentStrategy).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@SoulPancake
SoulPancake force-pushed the fix/release-immutable-releases branch from c784ff9 to c6168cf Compare October 29, 2026 15:52

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are identified for the immutable-release publishing update and chart version bump.

No open issues 🎉

What changed in this PR

Updates chart publishing to support GitHub immutable releases and advances the chart version so previously unreleased content can be published under a new tag.

Changes:

  • Upgrades the pinned chart-releaser action from v1.7.0 to v1.8.0, enabling asset uploads before release publication.
  • Bumps the chart from 0.3.18 to 0.3.19 to avoid the existing immutable releases.
File Description
charts/​openfga/​Chart.yaml Advances the chart version to 0.3.19.
.github/​workflows/​release.yml Updates the pinned chart-releaser action for immutable-release support.

Review effort: Balanced

@SoulPancake
SoulPancake merged commit 8228398 into main Oct 29, 2026
9 checks passed
@SoulPancake
SoulPancake deleted the fix/release-immutable-releases branch October 29, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants