fix(ci): attach assets when release changed from draft to published

[Andrey Kolkov (androndo)]

Release flow:

1. Megre PR's → drafter collects draft with changes.
2. Push version tag vX.Y.Z → build image and helm chart into GHCR.
3. When draft release (tag vX.Y.Z) become published → release-assets builds and attached to the release.

Summary by CodeRabbit

• Chores
  • Updated release workflow to attach generated install manifests when a release is published (instead of at creation), and clarified header comments documenting release-attachment behavior and backfill path.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 024cdf89-39aa-4571-8d54-2a5fb685dd68

📥 Commits

Reviewing files that changed from the base of the PR and between 949ede5 and d20927b.

📒 Files selected for processing (1)

• .github/workflows/release-assets.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/release-assets.yml

---

📝 Walkthrough

Walkthrough

This PR changes the GitHub Actions release workflow to attach generated install manifests when a release is published rather than when it is created, and updates header comments to document the new behavior and workflow_dispatch backfill path.

Changes

Release Workflow Event Trigger

Layer / File(s)	Summary
Release trigger event and documentation .github/workflows/release-assets.yml	Changed the release-assets workflow on.release.types from created to published and updated header comments to document the attachment behavior and workflow_dispatch backfill path.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit hops through CI tonight,
Waiting till publish to get it right.
Manifests cling when the bell is rung,
Workflow sings, the release is sprung. 🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the CI workflow to attach assets when a release transitions from draft to published status.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}