Skip to content

Release version 0.10.2 #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sébastien Duquette (sduquette-devolutions) merged 1 commit into from
Sep 14, 2026
Merged

Release version 0.10.2 #414

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)

## [Unreleased] -

## [0.10.2] - 2026-09-14

- Fix a double free in the C# wrapper
- Update dependencies chacha20poly1305 and dalek

## [0.10.0] - 2026-06-16

### Breaking Changes
Expand Down
12 changes: 6 additions & 6 deletions Cargo.lock
View file
Open in desktop

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
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
[workspace]
package.version = "0.10.1"
package.version = "0.10.2"
members = [
"cli",
"ffi",
Expand Down
7 changes: 7 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Release
This document describes the process to publish a new version of devolutions-crypto.

1. Update the changes in CHANGELOG.md.
2. Update the version number in Cargo.toml.
3. Make a commit for the new version number.
4. Use the "Deploy to production" workflows to publish the packages.
Loading