feat(suzuki-shunsuke/ghir): GitHub immutable release config

[scop]

Check List

• Read CONTRIBUTING.md
  • Read OSS Contribution Guide
• All commits are signed
  • This repository enables Require signed commits, so all commits must be signed
• Avoid force push
• Install and execute the package and confirm if the package works well
• Execute cmdx s to scaffold code

Summary by CodeRabbit

• Chores
  • Updated configuration to enable immutable release handling for GitHub artifacts.

[coderabbitai]

📝 Walkthrough

Walkthrough

Added github_immutable_release: true configuration to the github_artifact_attestations block in registry.yaml for the suzuki-shunsuke/ghir package, enabling immutable release handling for GitHub artifact attestations.

Changes

Cohort / File(s)	Summary
Registry Configuration pkgs/suzuki-shunsuke/ghir/registry.yaml	Added github_immutable_release: true flag under github_artifact_attestations to enable immutable release behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat(pnpm/pnpm): Github immutable release config #50084: Adds the same github_immutable_release: true configuration to another package's registry.yaml entry.
• feat(j178/prek): GitHub immutable release config #50075: Adds github_immutable_release: true setting to GitHub-release entries in package registry.yaml files.
• feat(owenlamont/ryl): GitHub artifact attestations config #49707: Modifies the github_artifact_attestations block by adding signer_workflow configuration in a related package.

Suggested labels

enhancement

Poem

🐰 A flag so small, just one line bright,
github_immutable_release shines in the night,
Registry hops with joy and ease,
Releases now locked with perfect peace! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description includes the required checklist template with some items checked (signed commits, avoid force push), but lacks written description details and several important checklist items remain unchecked.	Complete the checklist by checking read items and confirming package functionality, and add a written description explaining the purpose and impact of the github_immutable_release configuration change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat(suzuki-shunsuke/ghir): GitHub immutable release config' directly summarizes the main change: adding GitHub immutable release configuration to the registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@registry.yaml`:
- Around line 82932-82934: The YAML key github_immutable_release is currently a
sibling of github_artifact_attestations; move github_immutable_release into the
github_artifact_attestations mapping so it becomes a child entry (i.e., nest
github_immutable_release under github_artifact_attestations) to restore the
intended shape and comply with the registry.json schema; verify the resulting
mapping under github_artifact_attestations contains signer_workflow and
github_immutable_release together.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2eeab92f-e45e-4aca-818e-03595dffddb4

📥 Commits

Reviewing files that changed from the base of the PR and between d9443e7 and 05cc303.

📒 Files selected for processing (2)

• pkgs/suzuki-shunsuke/ghir/registry.yaml
• registry.yaml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Nest github_immutable_release under github_artifact_attestations.

Line 82934 is currently a sibling of github_artifact_attestations, not part of that mapping. That changes the YAML shape, so the new flag likely won't configure attestations as intended.

Suggested fix

         github_artifact_attestations:
           signer_workflow: suzuki-shunsuke/go-release-workflow/.github/workflows/release.yaml
-        github_immutable_release: true
+          github_immutable_release: true

As per coding guidelines, For registry.yaml configuration, use the JSON Schema defined at .ai/aqua/json-schema/registry.json.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	github_artifact_attestations:
	signer_workflow: suzuki-shunsuke/go-release-workflow/.github/workflows/release.yaml
	github_immutable_release: true
	github_artifact_attestations:
	signer_workflow: suzuki-shunsuke/go-release-workflow/.github/workflows/release.yaml
	github_immutable_release: true

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@registry.yaml` around lines 82932 - 82934, The YAML key
github_immutable_release is currently a sibling of github_artifact_attestations;
move github_immutable_release into the github_artifact_attestations mapping so
it becomes a child entry (i.e., nest github_immutable_release under
github_artifact_attestations) to restore the intended shape and comply with the
registry.json schema; verify the resulting mapping under
github_artifact_attestations contains signer_workflow and
github_immutable_release together.

[suzuki-shunsuke]

Thank you!