Prepare the 0.4.0 release. (#97)

Author: jsirois

CHANGES.md

@@ -1,5 +1,13 @@
 # Release Notes
 
+## 0.4.0
+
+This release supports use of the `scie-pants` binary in the Pants repo being defaulted to
+`PANTS_SOURCE=. pants` behavior; i.e.: If you run `pants` in the Pants repo, it will do what you
+probably expect: not run Pants from a released version (since the Pants repo specifies none), not
+prompt you to set `pants_version` (because that's almost surely not what you want), but run Pants
+from the local repo sources.
+
 ## 0.3.2
 
 This release fixes the Pants from sources feature added in 0.3.0 to forward command line arguments

Cargo.lock

@@ -6,7 +6,7 @@ members = [
 [package]
 name = "scie-pants"
 description = "Protects your Pants from the elements."
-version = "0.3.2"
+version = "0.4.0"
 edition = "2021"
 authors = [
     "John Sirois <[email protected]>",

Cargo.toml

@@ -111,11 +111,6 @@ The `scie-pants` binary will re-install versions of Pants you have already insta
 directory that is different from the `~/.cache/pants/setup` directory used by the `./pants` script.
 This is a one-time event per Pants version.
 
-The `scie-pants` does not work in the Pants repo itself. That repo has a special `./pants` script
-and declares no `pants_version`. As such, if you run `scie-pants` in the Pants repo, you'll be
-prompted to set up the latest stable version of Pants. You can just answer no and remember not to
-use `scie-pants` in the Pants repo.
-
 ## Solving Problems
 
 ### Try upgrading