feat: enable windows support for latest Zellij

[attakei]

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

Description

Summary

This PR is for enable to install Zellij into Windows on latest version (>=0.44.0).

Why do I require this

Zellij v0.44.0 (latest update in this PR) has published Windows executables.
I want to use this on Windows too, current registry definition only supports macos and linux.

Therefore, I edit registry that it can install on Windows by these steps.

• Regenerate registry by agrd s
• Remove checksum properties because uploaded checksums are not for archive files.

Refer to

• https://github.com/zellij-org/zellij/releases/tag/v0.44.0

Summary by CodeRabbit

• Chores
  • Added support for multiple Zellij releases (v0.44.0, v0.43.1, v0.5.1, v0.1.0-alpha).
  • Introduced version-specific distribution handling (different archive formats and asset names per release).
  • Improved cross-platform support including macOS, Linux (glibc and musl), and Windows with emulation and ZIP handling.

[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: c3221f79-5fec-4bdb-b973-ba35ed9d2efd

📥 Commits

Reviewing files that changed from the base of the PR and between d6992bf and 7e1fbbf.

📒 Files selected for processing (3)

• pkgs/zellij-org/zellij/pkg.yaml
• pkgs/zellij-org/zellij/registry.yaml
• registry.yaml

✅ Files skipped from review due to trivial changes (1)

• pkgs/zellij-org/zellij/pkg.yaml

🚧 Files skipped from review as they are similar to previous changes (2)

• registry.yaml
• pkgs/zellij-org/zellij/registry.yaml

---

📝 Walkthrough

Walkthrough

The package entries for zellij were expanded to include multiple explicit versions, and the registry entries were converted from a single static asset definition to a version_constraint/version_overrides model that selects assets, formats, platform replacements, and per-version overrides (including Windows/rosetta2 handling).

Changes

Cohort / File(s)	Summary
Package Version Declarations pkgs/zellij-org/zellij/pkg.yaml	Expanded package list from a single pinned entry to include additional explicit versions: v0.43.1, v0.5.1, and v0.1.0-alpha alongside v0.44.0.
Package Registry Configuration pkgs/zellij-org/zellij/registry.yaml, registry.yaml	Replaced an unconditional asset/format mapping with a version_constraint + version_overrides matrix. Each override defines per-version asset templates and formats (tar.gz, raw/mosaic, zip), modified supported_envs, platform replacement mappings, and OS-specific nested overrides (e.g., windows zip handling, linux musl asset names, rosetta2 flags).

Estimated Code Review Effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• Re-scaffold go-swagger/go-swagger #50454: Implements the same multi-version pkg.yaml expansion and registry.yaml version_overrides pattern for per-version assets and platform overrides.
• fix(google/go-jsonnet): support v0.22.0 asset naming change #50942: Adds version-specific asset templates and catch‑all rules in registry entries—closely mirrors the per-version asset/format changes.
• refactor: fix lint errors #50398: Converts a single asset mapping into a version_constraint/version_overrides structure with OS-specific overrides, similar to these changes.

Poem

🐇 I hopped through versions, neat and spry,

Assets dressed per-v, under sky,
Tarballs, mosaics, zips for Win,
Platform flags to tuck us in,
A carrot-coded registry sigh.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: enabling Windows support for the latest Zellij version (v0.44.0). It is clear, specific, and directly related to the primary objective of the PR.
Description check	✅ Passed	The description includes all required checklist items (both marked complete), a clear summary section, reasoning for the changes, and specific implementation details. It provides sufficient context about why Windows support was added and references the v0.44.0 release.
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.}

[coderabbitai]

🧹 Nitpick comments (1)

registry.yaml (1)

94335-94356: Redundant version override blocks can be merged.

The semver("<= 0.30.0") and semver("<= 0.43.1") blocks have identical configurations (same asset pattern, format, replacements, and supported_envs). Since aqua processes overrides in order, removing the <= 0.30.0 block would cause those versions to fall through to <= 0.43.1 with the same result.

♻️ Suggested simplification

-      - version_constraint: semver("<= 0.30.0")
-        asset: zellij-{{.Arch}}-{{.OS}}.{{.Format}}
-        format: tar.gz
-        replacements:
-          amd64: x86_64
-          arm64: aarch64
-          darwin: apple-darwin
-          linux: unknown-linux-musl
-        supported_envs:
-          - linux
-          - darwin
       - version_constraint: semver("<= 0.43.1")
         asset: zellij-{{.Arch}}-{{.OS}}.{{.Format}}
         format: tar.gz

🤖 Prompt for AI Agents

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

In `@registry.yaml` around lines 94335 - 94356, The two override entries with
version_constraint semver("<= 0.30.0") and semver("<= 0.43.1") are identical
(same asset: zellij-{{.Arch}}-{{.OS}}.{{.Format}}, format: tar.gz, replacements
and supported_envs) and can be merged by removing the redundant semver("<=
0.30.0") block; keep the broader semver("<= 0.43.1") entry so older versions
still match the same override, ensuring the asset, format, replacements and
supported_envs definitions from the remaining block
(zellij-{{.Arch}}-{{.OS}}.{{.Format}} / tar.gz / replacements / supported_envs)
are preserved in the file.

🤖 Prompt for all review comments with AI agents

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

Nitpick comments:
In `@registry.yaml`:
- Around line 94335-94356: The two override entries with version_constraint
semver("<= 0.30.0") and semver("<= 0.43.1") are identical (same asset:
zellij-{{.Arch}}-{{.OS}}.{{.Format}}, format: tar.gz, replacements and
supported_envs) and can be merged by removing the redundant semver("<= 0.30.0")
block; keep the broader semver("<= 0.43.1") entry so older versions still match
the same override, ensuring the asset, format, replacements and supported_envs
definitions from the remaining block (zellij-{{.Arch}}-{{.OS}}.{{.Format}} /
tar.gz / replacements / supported_envs) are preserved in the file.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 49f0661b-131f-4f09-b8fd-0eb4d0f628a7

📥 Commits

Reviewing files that changed from the base of the PR and between ce6980a and d6992bf.

📒 Files selected for processing (3)

• pkgs/zellij-org/zellij/pkg.yaml
• pkgs/zellij-org/zellij/registry.yaml
• registry.yaml

[suzuki-shunsuke]

Thank you!

[suzuki-shunsuke]

🚀 https://github.com/aquaproj/aqua-registry/releases/tag/v4.491.0