Release packages (#1170)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.3.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).
# config 0.1.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.
# knope 0.18.0 (2024-08-18)
## Breaking Changes

### Auto-update Cargo workspace dependencies when using default config

If using the Cargo workspace [default
configuration](https://knope.tech/reference/default-config/#cargo-workspaces),
Knope will now attempt to automatically update the version of workspace
members in dependencies _and_ the workspace `Cargo.lock`.

To avoid this, use `knope --generate` to create a manual config file and
customize the behavior.

### Don't create _any_ go module tags that match package names

Knope already avoided creating duplicate tags for Go modules which match
tags that would be created by the `Release` step for the package.
Now, Knope won't create a Go module tag if it matches a release tag for
_any_ configured package, to avoid potential conflicts.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Fixes

### Deduplicate release actions

Knope now collects all actions to be performed across all packages and
runs them at once with deduplication.

This means that if multiple packages write to the same `versioned_file`,
for example, the file will only be written
a single time.
Changesets will also only be deleted once, files will be staged to Git
only once, etc.

This mostly only impacts the output during `--dry-run` or `--verbose`,
but is especially important for the new
dependency updating and lockfile support.

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

Author: knope-bot-test[bot]

.changeset/auto_update_workspace_dependencies.md

@@ -10,6 +10,46 @@ The results are changes to the current directory, calls to external commands, an
 Notably, anything written to standard output or standard error
 (what you see in the terminal) is _not_ considered part of the public API and may change between any versions.
 
+## 0.18.0 (2024-08-18)
+
+### Breaking Changes
+
+#### Auto-update Cargo workspace dependencies when using default config
+
+If using the Cargo workspace [default configuration](https://knope.tech/reference/default-config/#cargo-workspaces),
+Knope will now attempt to automatically update the version of workspace members in dependencies _and_ the workspace `Cargo.lock`.
+
+To avoid this, use `knope --generate` to create a manual config file and customize the behavior.
+
+#### Don't create _any_ go module tags that match package names
+
+Knope already avoided creating duplicate tags for Go modules which match tags that would be created by the `Release` step for the package.
+Now, Knope won't create a Go module tag if it matches a release tag for _any_ configured package, to avoid potential conflicts.
+
+### Features
+
+#### Support for `Cargo.lock` in `versioned_files`
+
+Dependencies within a `Cargo.lock` [can now be updated](https://knope.tech/reference/config-file/packages#cargolock).
+
+#### Support for dependencies within `Cargo.toml`
+
+Dependencies within a `Cargo.toml` file [can now be updated](https://knope.tech/reference/config-file/packages/)
+as part of `versioned_files`.
+
+### Fixes
+
+#### Deduplicate release actions
+
+Knope now collects all actions to be performed across all packages and runs them at once with deduplication.
+
+This means that if multiple packages write to the same `versioned_file`, for example, the file will only be written
+a single time.
+Changesets will also only be deleted once, files will be staged to Git only once, etc.
+
+This mostly only impacts the output during `--dry-run` or `--verbose`, but is especially important for the new
+dependency updating and lockfile support.
+
 ## 0.17.0 (2024-08-04)
 
 ### Breaking Changes

.changeset/deduplicate_release_actions.md

@@ -9,7 +9,7 @@ strip = true
 [workspace.dependencies]
 changesets = { version = "0.3.0" }
 itertools = "0.13.0"
-knope-versioning = { path = "crates/knope-versioning", version = "0.2.0" }
+knope-versioning = { path = "crates/knope-versioning", version = "0.3.0" }
 miette = "7.2.0"
 relative-path = { version = "1.9.3", features = ["serde"] }
 serde = { version = "1.0.200", features = ["derive"] }

.changeset/dont_create_any_go_module_tags_that_match_package_names.md

@@ -1,3 +1,12 @@
+## 0.1.0 (2024-08-18)
+
+### Breaking Changes
+
+#### Support for dependencies within `Cargo.toml`
+
+Dependencies within a `Cargo.toml` file [can now be updated](https://knope.tech/reference/config-file/packages/)
+as part of `versioned_files`.
+
 ## 0.0.1 (2024-08-04)
 
 ### Features

.changeset/support_for_cargolock_in_versioned_files.md

@@ -1,7 +1,7 @@
 [package]
 name = "knope-config"
 description = "A library for handling common configuration of Knope"
-version = "0.0.1"
+version = "0.1.0"
 authors = ["Dylan Anthony <[email protected]>"]
 edition = "2021"
 license = "MIT"