bash-env-nushell has effectively replaced the old nu_plugin_bash_env path for a lot of people — we're pointing new installs at the module instead of the plugin.
I'm listing 0.19.0 in the Numan registry. Because there's no release asset on the tag yet, we packaged the repo root ourselves and host that zip on our registry releases. It works, but I'd rather pin against something you own.
The specific thing that makes me nervous about not having an uploaded asset: consumers that record sha256(url) will pick GitHub's auto-generated tag archive if we don't have anything else, and those archives aren't promised to stay byte-stable. One infrastructure change on GitHub's side and every pinned install looks corrupt.
If you're open to it, an uploaded bash-env-nushell-{version}.zip on future tags would be ideal — flat layout is fine:
bash-env-nushell-0.19.0/
├── bash-env.nu # our entry point (not mod.nu — intentional)
├── README.md
└── …
Totally fine if you'd rather not maintain release artifacts; we'll keep mirroring. Separate note: we already tell users they need bash-env-json on PATH — not asking you to bundle that.
Happy to contribute a tag → zip GitHub Action if that lowers the maintenance cost.
bash-env-nushellhas effectively replaced the oldnu_plugin_bash_envpath for a lot of people — we're pointing new installs at the module instead of the plugin.I'm listing 0.19.0 in the Numan registry. Because there's no release asset on the tag yet, we packaged the repo root ourselves and host that zip on our registry releases. It works, but I'd rather pin against something you own.
The specific thing that makes me nervous about not having an uploaded asset: consumers that record
sha256(url)will pick GitHub's auto-generated tag archive if we don't have anything else, and those archives aren't promised to stay byte-stable. One infrastructure change on GitHub's side and every pinned install looks corrupt.If you're open to it, an uploaded
bash-env-nushell-{version}.zipon future tags would be ideal — flat layout is fine:Totally fine if you'd rather not maintain release artifacts; we'll keep mirroring. Separate note: we already tell users they need
bash-env-jsonon PATH — not asking you to bundle that.Happy to contribute a tag → zip GitHub Action if that lowers the maintenance cost.