[pascalinthecloud]

Resolves #2746

---

Before the change?

• Immutable releases could not be managed for a repository.

After the change?

• New github_repository_immutable_releases resource. It is a separate resource rather than a github_repository attribute because the setting has its own endpoints.
• Uses the rename-safe repository / repository_id / diffRepository pattern, so renaming the repository updates in place.
• GitHub documents a 404 from GET /repos/{owner}/{repo}/immutable-releases when the feature is disabled, but it currently returns 200 {"enabled": false}. On a 404, Read looks the repository up and only drops the resource from state if the repository is gone, so it works with either behaviour.

Testing: TestAccGithubRepositoryImmutableReleases passes in organization mode. I also applied it manually with a local build: a release published afterwards returns "immutable": true, and a re-plan shows no drift.

The org-level setting is handled separately in #3227.

This PR was written with help from an AI coding assistant. I have reviewed and tested the changes.

Pull request checklist

• Schema migrations have been created if needed (example)
• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi, and thank you for this contribution!

This repo is maintained by GitHub and community members on a best-effort basis. We'll get to this as soon as we can.

You can help us prioritize by joining the discussion on open issues and PRs, sharing details on the changes you need, and reviewing other contributions.

---

_{🤖 This is an automated message.}