Skip to content

Commit

Permalink
chore: release
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored Jan 30, 2025
1 parent 542e603 commit d4ace6f
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 2 deletions.
13 changes: 13 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.0.6](https://github.com/eopb/cargo-override/compare/v0.0.5...v0.0.6) - 2025-01-30

### Other

- Upgrade to Winnow 0.7 ([#183](https://github.com/eopb/cargo-override/pull/183))
- bump the cargo-dependencies group with 4 updates ([#157](https://github.com/eopb/cargo-override/pull/157))
- bump the github-dependencies group with 3 updates ([#156](https://github.com/eopb/cargo-override/pull/156))
- Add clippy to CI ([#154](https://github.com/eopb/cargo-override/pull/154))
- bump the github-dependencies group with 2 updates ([#153](https://github.com/eopb/cargo-override/pull/153))
- bump the cargo-dependencies group with 2 updates ([#152](https://github.com/eopb/cargo-override/pull/152))
- bump anyhow from 1.0.88 to 1.0.89 in the cargo-dependencies group ([#150](https://github.com/eopb/cargo-override/pull/150))
- bump the github-dependencies group with 2 updates ([#149](https://github.com/eopb/cargo-override/pull/149))

## [0.0.5](https://github.com/eopb/cargo-override/compare/v0.0.4...v0.0.5) - 2024-09-14

### Added
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "cargo-override"
version = "0.0.5"
version = "0.0.6"
edition = "2021"
rust-version = "1.79"
license = "Apache-2.0 OR MIT"
Expand Down

0 comments on commit d4ace6f

Please sign in to comment.