Releases: knope-dev/knope
config 0.2.2 (2025-04-05)
Features
- Print each step before it runs when
--verboseis set (#1399)
versioning 0.4.0 (2025-04-05)
Breaking Changes
- Change the return type of
Config::defaults
Features
Add support for Tauri config files
Supports Tauri configuration files in json format named tauri.conf.json, tauri.macos.conf.json, tauri.windows.conf.json, and tauri.linux.conf.json.
knope 0.19.1 (2025-04-05)
Features
Add support for Tauri config files
Supports Tauri configuration files in json format named tauri.conf.json, tauri.macos.conf.json, tauri.windows.conf.json, and tauri.linux.conf.json.
knope 0.19.0 (2025-03-23)
Breaking Changes
Updated config locations
Knope is internally using a newer crate for storing persistent config, so some things (like GitHub tokens) may need to
be updated on next run.
Documentation
Document creating releases with Knope Bot
versioning 0.3.3 (2025-03-12)
knope 0.18.5 (2025-03-12)
versioning 0.3.2 (2025-03-08)
Features
Add basic support for versioning of pom.xml files
pom.xml must contain a <version> field in the <project> section.
Dependencies and multi-module projects are not yet supported.
Fixes
Don't normalize existing changeset file names
When a new change file is created via CreateChangeFile,
its name is generated by converting the summary of the change to all lowercase letters and underscores.
This same normalization was happening when opening an existing change file, which prevented that change file from
being deleted during a PrepareRelease step if it didn't match the normalized version
(for example, was created with a different tool or by hand).
This has been fixed.
Fixes #1340
Notes
- Update to Rust edition 2024 and MSRV 1.85
knope 0.18.4 (2025-03-08)
Features
Add basic support for versioning of pom.xml files
pom.xml must contain a <version> field in the <project> section.
Dependencies and multi-module projects are not yet supported.
Fixes
Don't normalize existing changeset file names
When a new change file is created via CreateChangeFile,
its name is generated by converting the summary of the change to all lowercase letters and underscores.
This same normalization was happening when opening an existing change file, which prevented that change file from
being deleted during a PrepareRelease step if it didn't match the normalized version
(for example, was created with a different tool or by hand).
This has been fixed.
Fixes #1340
Notes
- Update to Rust edition 2024 and MSRV 1.85
config 0.2.1 (2025-03-08)
Notes
- Update to Rust edition 2024 and MSRV 1.85
knope 0.18.3 (2025-01-21)
Fixes
- Improve error messages when GitHub releases fail