sayanarijit · sayanarijit · Mar 21, 2025 · Mar 21, 2025 · Mar 21, 2025
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -8,7 +8,7 @@ path = './benches/criterion.rs'
 
 [package]
 name = 'xplr'
-version = '0.21.10'
+version = '1.0.0'
 authors = ['Arijit Basu <hi@arijitbasu.in>']
 edition = '2021'
 description = 'A hackable, minimal, fast TUI file explorer'
@@ -22,18 +22,18 @@ categories = ['command-line-interface', 'command-line-utilities']
 include = ['src/**/*', 'docs/en/src/**/*', 'LICENSE', 'README.md']
 
 [dependencies]
-libc = "0.2.169"
+libc = "0.2.171"
 humansize = "2.1.3"
 natord = "1.0.9"
-anyhow = "1.0.95"
+anyhow = "1.0.97"
 serde_yaml = "0.9.34"
 crossterm = { version = "0.28.1", features = [], default-features = false }
 ansi-to-tui = "7.0.0"
 regex = "1.11.1"
 gethostname = "1.0.0"
 serde_json = "1.0.138"
 path-absolutize = "3.1.1"
-which = "7.0.1"
+which = "7.0.2"
 nu-ansi-term = "0.50.1"
 textwrap = "0.16.1"
 snailquote = "0.3.1"

diff --git a/docs/en/src/upgrade-guide.md b/docs/en/src/upgrade-guide.md
@@ -3,7 +3,7 @@
 When you upgrade xplr, you might see an error like this
 
 ```
-Incompatible script version in: /home/sayanarijit/.config/xplr/init.lua. The script version is: 0.9.0, the required version is: 0.10.1. Visit https://github.com/sayanarijit/xplr/wiki/Upgrade-Guide
+Incompatible script version in: /home/user/.config/xplr/init.lua. The script version is: 0.21.0, the required version is: 1.0.0. Visit https://xplr.dev/en/upgrade-guide
 ```
 
 All you need to do is follow the [instructions][1] starting from
@@ -37,14 +37,28 @@ e.g.
   e.g. `app-1.0.0` with `config-1.1.0`. But vice versa is fine.
 - `1.0.0` -> `x.x.x`: Not compatible at all.
 
-Note that until we're `v1`, we'll be using the `{minor}` version number as
-`{major}`, and the `{patch}` number as `{minor}` to determine
-compatibility.
-
 </details>
 
 ### Instructions
 
+#### [v0.21.10][49] -> [v0.1.0][51]
+
+- This release added a new message `TryCompletePath` which will try to complete
+  the path in the input buffer. You should use this message instead of the
+  fragile `xplr.fn.builtin.try_complete_path` Lua function, which will still
+  keep working (with a warning log message) for compatibility reasons.
+
+**ANNOUNCEMENT:**
+
+This is not really a breaking change, but a declaration of the first stable
+release. You cat set `version = "1.0.0"` in your config file without any
+concern. With this release, xplr v1 can be considered feature complete.
+
+As of now, there is no plan for xplr v2, and so, the project will enter cleanup
+and maintenance mode. Thank you everyone, who directly or indirectly contributed
+to xplr, for all your effort, support and feedback. Looking forward to more
+such collaborations in the future.
+
 #### [v0.20.2][48] -> [v0.21.10][49]
 
 - Some plugins might stop rendering colors. Wait for them to update.
@@ -531,3 +545,4 @@ Else do the following:
 [48]: https://github.com/sayanarijit/xplr/releases/tag/v0.20.2
 [49]: https://github.com/sayanarijit/xplr/releases/tag/v0.21.10
 [50]: https://github.com/lotabout/skim#search-syntax
+[51]: https://github.com/sayanarijit/xplr/releases/tag/v1.0.0
diff --git a/src/lua/mod.rs b/src/lua/mod.rs
@@ -14,7 +14,7 @@ use std::fs;
 pub mod util;
 
 const DEFAULT_LUA_SCRIPT: &str = include_str!("../init.lua");
-const UPGRADE_GUIDE_LINK: &str = "https://xplr.dev/en/upgrade-guide.html";
+const UPGRADE_GUIDE_LINK: &str = "https://xplr.dev/en/upgrade-guide";
 
 pub fn serialize<T: Serialize + Sized>(
     lua: &mlua::Lua,
@@ -153,24 +153,24 @@ mod tests {
         assert!(check_version(VERSION, "foo path").is_ok());
 
         // Current release if OK
-        assert!(check_version("0.21.10", "foo path").is_ok());
+        assert!(check_version("1.0.0", "foo path").is_ok());
 
         // Prev major release is ERR
-        // - Not yet
+        assert!(check_version("0.20.0", "foo path").is_err());
 
         // Prev minor release is ERR (Change when we get to v1)
-        assert!(check_version("0.20.10", "foo path").is_err());
+        // assert!(check_version("1.-1.0", "foo path").is_err());
 
         // Prev bugfix release is OK
-        assert!(check_version("0.21.9", "foo path").is_ok());
+        // assert!(check_version("1.0.-1", "foo path").is_ok());
 
         // Next major release is ERR
-        assert!(check_version("1.20.10", "foo path").is_err());
+        assert!(check_version("2.0.0", "foo path").is_err());
 
         // Next minor release is ERR
-        assert!(check_version("0.22.10", "foo path").is_err());
+        assert!(check_version("1.1.0", "foo path").is_err());
 
         // Next bugfix release is ERR (Change when we get to v1)
-        assert!(check_version("0.21.11", "foo path").is_err());
+        assert!(check_version("1.0.1", "foo path").is_err());
     }
 }