starting v3.13.0, mvdan/sh no longer includes a sha256sums.txt asset

[adilsyed518]

… disabling checksum for new version

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

As of version 3.13.0 mvdan/sh stopped publishing sha256sum.txt asset as github now provides digest natively. So, I am removing the checksum for new version.
See notes: https://github.com/mvdan/sh/releases/tag/v3.13.0

Fixes #50079

Summary by CodeRabbit

• New Features

  • Added shfmt tooling support across darwin, linux, and amd64 platforms.

• Chores

  • Updated mvdan/sh package to v3.13.0.
  • Added explicit mvdan/sh v3.12.0 entry.
  • Adjusted version constraints for package compatibility.

[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: 9cc90241-6786-4494-ac20-3ef978999368

📥 Commits

Reviewing files that changed from the base of the PR and between 4539f27 and 7339864.

📒 Files selected for processing (3)

• pkgs/mvdan/sh/pkg.yaml
• pkgs/mvdan/sh/registry.yaml
• registry.yaml

---

📝 Walkthrough

Walkthrough

Updates mvdan/sh package configuration across three YAML files. Upgrades primary dependency from v3.12.0 to v3.13.0, establishes explicit v3.12.0 entry, tightens version constraints, and adds new package entries with explicit file listings for shfmt across supported platforms.

Changes

Cohort / File(s)	Summary
mvdan/sh Package Configuration pkgs/mvdan/sh/pkg.yaml, pkgs/mvdan/sh/registry.yaml, registry.yaml	Version upgrade from v3.12.0 to v3.13.0 as primary entry. Adds explicit v3.12.0 package entry. Constrains first registry entry to semver("<= 3.12.0"). Introduces new package/github_release blocks with explicit shfmt file configuration and platform support (darwin, linux, amd64).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A version hop from three-twelve to thirteen we see,
New entries sprouting for compatibility,
Constraints now tighter, files made explicit—
The shfmt shall flow where assets aren't implicit! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: mvdan/sh v3.13.0 no longer includes sha256sums.txt asset, which is the core reason for the version update and checksum handling changes.
Description check	✅ Passed	The PR description includes the required checklist template and provides a clear explanation of why the change is needed, referencing the upstream release notes and the fix target.
Linked Issues check	✅ Passed	The PR changes meet the objective of issue #50079: updating mvdan/sh from v3.12.0 to v3.13.0 and removing checksum constraints to handle the missing sha256sums.txt asset, allowing CI to succeed without the absent asset.
Out of Scope Changes check	✅ Passed	All changes are directly related to the issue objective. The modifications update mvdan/sh package versions, adjust version constraints, and add new package entries to accommodate the missing checksum asset, with no unrelated changes present.
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.}

[adilsyed518]

Bot PR failing: #50045

[suzuki-shunsuke]

Thank you for your contribution!