bump version to 1.8.0 (#1348)

Author: zsol

CHANGELOG.md

@@ -1,3 +1,24 @@
+# 1.8.0 - 2025-05-27
+
+## Added
+* Allow configuring empty formatter lists in codemod CLI by @ngoldbaum in https://github.com/Instagram/LibCST/pull/1319
+* Publish several new binary wheels
+  * macos intel by @hadialqattan in https://github.com/Instagram/LibCST/pull/1316
+  * windows arm64 by @zsol in https://github.com/Instagram/LibCST/pull/1304
+  * 3.13 CPython free-threaded by @zsol in https://github.com/Instagram/LibCST/pull/1333
+  * (only on [test.pypi.org](https://test.pypi.org/project/libcst/#history)) 3.14 and 3.14 CPython free-threaded by @amyreese and @zsol in https://github.com/Instagram/LibCST/pull/1345 and https://github.com/Instagram/LibCST/pull/1331
+* Enable support for free-threaded CPython by @zsol in https://github.com/Instagram/LibCST/pull/1295 and https://github.com/Instagram/LibCST/pull/1335
+
+## Updated
+* update pyo3 to 0.25 by @ngoldbaum in https://github.com/Instagram/LibCST/pull/1324
+* Replace multiprocessing with ProcessPoolExecutor by @zsol in https://github.com/Instagram/LibCST/pull/1294
+* Support pipe syntax for Union types in codegen by @zsol in https://github.com/Instagram/LibCST/pull/1336
+
+## New Contributors
+* @hadialqattan made their first contribution in https://github.com/Instagram/LibCST/pull/1316
+
+**Full Changelog**: https://github.com/Instagram/LibCST/compare/v1.7.0...v1.8.0
+
 # 1.7.0 - 2025-03-13
 
 ## Added

MAINTAINERS.md

@@ -0,0 +1,11 @@
+# How to make a new release
+
+1. Add a new entry to `CHANGELOG.md` (I normally use the [new release page](https://github.com/Instagram/LibCST/releases/new) to generate a changelog, then manually group)
+    1. Follow the existing format: `Fixed`, `Added`, `Updated`, `Deprecated`, `Removed`, `New Contributors` sections, and the full changelog link at the bottom.
+    1. Mention only user-visible changes - improvements to CI, tests, or development workflow aren't noteworthy enough
+    1. Version bumps are generally not worth mentioning with some notable exceptions (like pyo3)
+    1. Group related PRs into one bullet point if it makes sense
+2. manually bump versions in `Cargo.toml` files in the repo
+3. make a new PR with the above changes, get it reviewed and landed
+4. make a new release on Github, create a new tag on publish, and copy the contents of the changelog entry in there
+5. after publishing, check out the repo at the new tag, and run `cd native; cargo +nightly publish -Z package-workspace -p libcst_derive -p libcst`

native/Cargo.lock

@@ -5,7 +5,7 @@
 
 [package]
 name = "libcst"
-version = "1.7.0"
+version = "1.8.0"
 authors = ["LibCST Developers"]
 edition = "2018"
 rust-version = "1.70"
@@ -42,7 +42,7 @@ peg = "0.8.5"
 annotate-snippets = "0.11.5"
 regex = "1.11.1"
 memchr = "2.7.4"
-libcst_derive = { path = "../libcst_derive", version = "1.6.0" }
+libcst_derive = { path = "../libcst_derive", version = "1.8.0" }
 
 [dev-dependencies]
 criterion = { version = "0.5.1", features = ["html_reports"] }

native/libcst/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "libcst_derive"
-version = "1.7.0"
+version = "1.8.0"
 edition = "2018"
 description = "Proc macro helpers for libcst."
 license = "MIT"