fix(google/go-jsonnet): support v0.22.0 asset naming change

[tak848]

Check List

• Read CONTRIBUTING.md
  • ⚠️ Avoid force push
  • ⚠️ Use argd s command when adding new packages
• Install and execute the package and confirm if the package works well

google/go-jsonnet v0.22.0 removed GoReleaser archive naming overrides (google/go-jsonnet#848), which changed the release asset naming convention.

v0.21.0: go-jsonnet_Linux_x86_64.tar.gz (capitalized OS, x86_64)
v0.22.0: go-jsonnet_0.22.0_linux_amd64.tar.gz (lowercase OS, standard Go arch, version in name)

This causes no asset found errors when installing v0.22.0 with the current registry definition.

Changes

• Pin the existing catchall version_constraint: "true" to Version == "v0.21.0"
• Add a new version_constraint: "true" entry for v0.22.0+ with asset template go-jsonnet_{{trimV .Version}}_{{.OS}}_{{.Arch}}.{{.Format}} (no replacements needed since v0.22.0 uses GoReleaser defaults matching aqua defaults)
• Update pkg.yaml test versions (add v0.22.0 as latest, add v0.21.0 as old version test)

Summary by CodeRabbit

• Chores
  • Added support for go-jsonnet v0.22.0 while retaining earlier v0.x releases for compatibility.
  • Updated registry selection rules to pick the appropriate release asset per version for more reliable installs.
  • Added checksum validation for release artifacts to improve integrity and security of package installations.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 15a33189-b1ec-4216-b0ae-3f17a899b2ff

📥 Commits

Reviewing files that changed from the base of the PR and between 879128b and 501d00d.

📒 Files selected for processing (3)

• pkgs/google/go-jsonnet/pkg.yaml
• pkgs/google/go-jsonnet/registry.yaml
• registry.yaml

---

📝 Walkthrough

Walkthrough

Updated go-jsonnet package pins and registry selection: bumped a package entry to v0.22.0, added an explicit v0.21.0 entry, and split registry overrides so v0.21.0 uses a specific asset template while a catch-all uses trimmed-version asset names with checksum verification.

Changes

Cohort / File(s)	Summary
Package pins pkgs/google/go-jsonnet/pkg.yaml	Updated google/go-jsonnet@v0.21.0 → google/go-jsonnet@v0.22.0 and added an explicit google/go-jsonnet entry pinned to v0.21.0.
Package registry override (package-level) pkgs/google/go-jsonnet/registry.yaml	Replaced a catch-all version_constraint: "true" with a Version == "v0.21.0" override using non-trimmed asset names; added a new catch-all override that uses trimV .Version in asset names and a checksums.txt sha256 block.
Global registry entries registry.yaml	Adjusted github_release entries: added a specific Version == "v0.21.0" selection for existing asset naming and a new catch-all version_constraint: "true" entry using trimmed-version asset names plus checksum verification (checksums.txt, sha256).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• refactor: fix lint errors #50398 — Similar changes to github_release package entries and asset template/checksum handling in registry.yaml.

Poem

🐰 A hop from twenty-one to twenty-two,

I paired the pins and tuned the view,
Trimmed names sing and checksums hum,
Two versions bobbing, neat and plumb,
The burrow’s tidy work is through.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: supporting v0.22.0 asset naming changes in google/go-jsonnet package registry configuration.
Description check	✅ Passed	The description provides clear explanation of the problem (asset naming change in v0.22.0), the specific asset naming differences between versions, the root cause, implementation details, and all changes made to resolve the issue.
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

---

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!