Adding nu version to scripts

[TheCodeLamp]

Hello, a recent commit (446f06f) broke the ssh custom completion for nu version 0.99.1 (the one shipped by dnf and fedora). This isn't a huge issue and I just downloaded the previous version.
However, it got me thinking, should the version of nu the script was developed for be commented in the script?
Ideally the script should display what versions of nu it works for, but this is unfeasible, probably.

[fdncred]

Not sure how that could happen really. Most people try to stay updated with the latest changes.

[cosineblast]

When I need my scripts to be versioned correctly (regardless of the language I'm using), I usually use the nix tool to get the right version for the programs the script uses, it's similar to python's venv, but works with most programs.

For instance, if you want to make so that your script uses a specific version of nushell when executed, you can use a nix shebang that refers to a specific commit hash of the nix package repository:

#! /usr/bin/env nix
#! nix shell github:nixos/nixpkgs/21808d22b1cda1898b71cf1a1beb524a97add2c4#nushell --command nu

#                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# This is the commit hash of the nix revision that has the 0.101.0 version of nushell
# you can find the hashes of other versions here:
# https://lazamar.co.uk/nix-versions/?channel=nixpkgs-unstable&package=nushell

print $"hi from (nu --version)"

Then run the script:

$ chmod +x script.nu
$ ./script.nu
hi from 0.101.0

[TheCodeLamp]

I was just thinking that adding a # created with nu version: 0.102.0 to the top of the file. This was just an idea to make it easier to find the last functional hash for your version.
I've actually solved this issue by just using carapace instead :P

[fdncred]

Authors are welcome to put that in the scripts they submit.

[hongquan]

Thank you. Those SSH completion changes were made by me. I will update my scripts to have that compatibility note.