Cut release for version 0.25.0

Author: Naatan

changelog.md

@@ -2,30 +2,43 @@
 
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres
 to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Unreleased
+## 0.25.0
 
-Available on channel `master`
+Available on channel: `beta` (`state update --set-channel beta`)
+
+**Warning:** This update will force a change to your activestate.yaml which is
+incompatible with earlier state tool versions. As long as everyone on your
+project updates their state tool there should be no interruption to your
+workflow.
 
 ### Added
 
 - New command `state cve` allows for reviewing security vulnerabilities on your
   project ([PR #1209](https://github.com/ActiveState/cli/pull/1209))
 - You can now specify a package version when calling `state info`,
   eg. `state info <name>@<version>` ([PR #1201](https://github.com/ActiveState/cli/pull/1201))
-- You can now specify a new project name by running `state pull --set-project OWNER/NAME` (primarily for converting
+- You can now specify a new project name by
+  running `state pull --set-project OWNER/NAME` (primarily for converting
   headless projects) ([PR #1198](https://github.com/ActiveState/cli/pull/1198))
 - You can now switch between update channels
   via `state update --set-channel` ([PR #1190](https://github.com/ActiveState/cli/pull/1190))
+- State tool now supports branches via flags in `state activate` and
+  the `state branch` subcommand. See `state branch --help` for more information.
 
 ### Changed
 
-- Activating a new project non-interactively no longer makes that project "default" (you can pass the `--default` flag
-  for this use-case) ([PR #1210](https://github.com/ActiveState/cli/pull/1210))
-- The user experience of `state secrets` is now consistent with the rest of the State
-  Tool ([PR #1197](https://github.com/ActiveState/cli/pull/1197))
+- Activating a new project non-interactively no longer makes that project "
+  default" (you can pass the `--default` flag for this
+  use-case) ([PR #1210](https://github.com/ActiveState/cli/pull/1210))
+- The user experience of `state secrets` is now consistent with the rest of the
+  State Tool ([PR #1197](https://github.com/ActiveState/cli/pull/1197))
+- `state import` now updates your runtime, so you don't need to re-activate
+  after importing
+  anymore ([PR #1241](https://github.com/ActiveState/cli/pull/1241))
 
 ### Fixed
 
@@ -37,6 +50,18 @@ Available on channel `master`
   project ([PR #1210](https://github.com/ActiveState/cli/pull/1210))
 - Fixed issue where `state activate` sometimes used the wrong
   activestate.yaml ([PR #1194](https://github.com/ActiveState/cli/pull/1194))
+- Fixed issue where `state info owner/name` would fail if not currently in a
+  project directory ([PR #1255](https://github.com/ActiveState/cli/pull/1255))
+- Fixed issue where running tooling from the global default project with
+  the `-v` flag would spew out state tool debug
+  info ([PR #1239](https://github.com/ActiveState/cli/pull/1239))
+- Fixed issue where sometimes perl/python is still pointing at the system
+  install after
+  activation ([PR #1238](https://github.com/ActiveState/cli/pull/1238))
+- Fix issue where state tool sometimes throws "panic" errors when updating the
+  configuration ([PR #1232](https://github.com/ActiveState/cli/pull/1232))
+- Fix issue where `state activate` sometimes throws a "
+  panic" ([PR #1229](https://github.com/ActiveState/cli/pull/1229))
 
 ### Deprecated
 

version.txt

@@ -1 +1 @@
-0.24.2
+0.25.0