feat(dprint/dprint): GitHub immutable release config

[scop]

https://github.com/dprint/dprint/releases

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

• Updates
  • Downgraded dprint to version 0.51.1 from 0.52.0
  • Added support for older dprint versions (< 0.52.0) with platform-specific configurations
  • Enhanced release stability with immutable release tracking

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated dprint package configuration to support versions below 0.52.0, adding platform-specific asset replacements and checksums across registry files. Enabled immutable release behavior and downgraded the main package entry from version 0.52.0 to 0.51.1.

Changes

Cohort / File(s)	Summary
Package Declaration pkgs/dprint/dprint/pkg.yaml	Updated primary dprint/dprint entry from version 0.52.0 to 0.51.1 with explicit version field.
Registry Configuration pkgs/dprint/dprint/registry.yaml, registry.yaml	Added new version constraint block for semver("< 0.52.0") with platform-specific replacements (amd64, arm64, darwin, linux, windows), asset references, Windows ARM emulation flag, and SHA256 checksums. Enabled immutable release behavior (github_immutable_release: true) for the universal release entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

enhancement

Poem

🐰 Hop and hop, version constraints flow,
Platform-specific paths steal the show,
Checksums verified from top to toe,
Immutable releases now let dprint glow!
📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description includes the standard checklist template and a link to dprint releases, but lacks substantive details about the changes, rationale, or what the PR accomplishes.	Add a meaningful description explaining what changes are being made (e.g., adding version constraint semver < 0.52.0, enabling immutable releases), why these changes are necessary, and what impact they have on the dprint package configuration.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding GitHub immutable release configuration for dprint/dprint.
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.}

[suzuki-shunsuke]

Thank you always!