Skip to content

Commit

Permalink
chore(rustic_core): release v0.6.1 (#363)
Browse files Browse the repository at this point in the history
## 🤖 New release
* `rustic_core`: 0.6.0 -> 0.6.1 (✓ API compatible changes)

<details><summary><i><b>Changelog</b></i></summary><p>

## `rustic_core`
<blockquote>

##
[0.6.1](rustic_core-v0.6.0...rustic_core-v0.6.1)
- 2024-11-19

### Added

- make FilePolicy usable in cli and config

### Fixed

- *(error)* add missing context to error in cache backend
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/MarcoIeni/release-plz/).

Co-authored-by: rustic-release-plz[bot] <182542030+rustic-release-plz[bot]@users.noreply.github.com>
  • Loading branch information
rustic-release-plz[bot] authored Nov 19, 2024
1 parent b18979c commit 22a898c
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 2 deletions.
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.

10 changes: 10 additions & 0 deletions crates/core/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

All notable changes to this project will be documented in this file.

## [0.6.1](https://github.com/rustic-rs/rustic_core/compare/rustic_core-v0.6.0...rustic_core-v0.6.1) - 2024-11-19

### Added

- make FilePolicy usable in cli and config

### Fixed

- *(error)* add missing context to error in cache backend

## [0.6.0](https://github.com/rustic-rs/rustic_core/compare/rustic_core-v0.5.5...rustic_core-v0.6.0) - 2024-11-18

### Added
Expand Down
2 changes: 1 addition & 1 deletion crates/core/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "rustic_core"
version = "0.6.0"
version = "0.6.1"
authors = ["the rustic-rs team"]
categories = ["data-structures", "encoding", "filesystem"]
documentation = "https://docs.rs/rustic_core"
Expand Down

0 comments on commit 22a898c

Please sign in to comment.