Repository navigation
Uploaded zip for tag releases? #50
Description
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.
Activity
tesujimath commentedon Jul 6, 2026
Totally happy for you to contribute a PR to do this. Sorry I don’t have the capacity for that myself just now.
Pleased to see this is useful! 😁
tonythethompson commentedon Jul 6, 2026
Thanks! I'll open a PR that adds a tag-triggered workflow uploading \bash-env-nushell-{version}.zip\ to GitHub Releases (same pattern as vyadh/nutest). Once a release ships we'll point the Numan registry at your upstream asset and drop the registry-hosted mirror.
tonythethompson commentedon Jul 7, 2026
Yes — this is exactly what we needed. I pulled
bash-env-nushell-0.19.0.zipfrom the0.19.0release and verified:bash-env-nushell-0.19.0/bash-env.nu(matches our entry path)8d5c18b9…)I'll point the Numan registry at your upstream release URL and drop our registry-hosted mirror for 0.19.0. Thanks for shipping this — and for the offer to take a PR for future tags; happy to send one if you still want automation on your side.
tesujimath commentedon Jul 7, 2026
Isn't the future tags case already addressed? There's a trigger here for on: push: tags. What am I missing?
tonythethompson commentedon Jul 10, 2026
You're right, nothing missing on your side. The
push: tagstrigger in #51 covers future releases automatically;workflow_dispatchwas only for backfilling 0.19.0.My last line about "happy to send a PR for automation" was stale wording from before #51 landed. Sorry for the noise. We're all set.