chore: update quiver to 0.3.3

Author: freepicheep

CHANGELOG.md

@@ -1,15 +1,19 @@
 # Unreleased
 
+# Version 0.3.3 (2026-03-06)
+
 ## Added
 
 - Nu plugins are now registered whenever they are installed, whether that is through `qv run`, `qv add-plugin`, or `qv install`. This means you can literally just clone a quiver project and run `qv run your-project/amazing_things.nu` and it will work, even if you are using Nu plugins.
 
 ## Fixed
 - `qv run` properly sets the `--plugin-config` when running `nu`.
+- Some issues with plugins being stale in the lockfile when the `nu-version` changed in the `nupackage.toml`.
 
 ## Changed
 
 - Quiver will always download the version of nu specified for a project, even if that version matches your current global installation in PATH. Why? Because if we symlink to your version in PATH at Nu 0.110.0, and you update to Nu 0.111.0, the symlink in your project's `.nu-env/bin/` will now be at 0.111.0 while your project is still at 0.110.0.
+- Quiver is now licensed under MIT or Apache 2.0, at your option.
 
 # Version 0.3.2 (2026-03-05)
 

Cargo.lock

@@ -1,18 +1,16 @@
 [package]
 name = "quiver"
-version = "0.3.2"
+version = "0.3.3"
 edition = "2024"
 description = "A module manager for Nushell"
 license = "MIT"
 repository = "https://github.com/freepicheep/quiver"
 homepage = "https://github.com/freepicheep/quiver"
 
 [dependencies]
-clap = { version = "4", features = ["derive"] }
 dirs = "6"
 git2 = "0.20"
 hex = "0.4"
-serde = { version = "1", features = ["derive"] }
 semver = "1"
 serde_json = "1"
 sha2 = "0.10"
@@ -24,9 +22,20 @@ console = "0.16.2"
 flate2 = "1"
 tar = "0.4"
 xz2 = "0.1"
-zip = { version = "0.6", default-features = false, features = ["deflate"] }
 
-# The profile that 'dist' will build with
+[dependencies.clap]
+version = "4"
+features = ["derive"]
+
+[dependencies.serde]
+version = "1"
+features = ["derive"]
+
+[dependencies.zip]
+version = "0.6"
+default-features = false
+features = ["deflate"]
+
 [profile.dist]
 inherits = "release"
 lto = "thin"