Releases: knope-dev/knope
config 0.3.1 (2025-12-02)
versioning 0.6.0 (2025-11-03)
Breaking Changes
VersionedFileConfig::new()signature changed to support Regex files
knope 0.21.5 (2025-11-03)
Features
Add support for updating version numbers in arbitrary text files using regex patterns. You can now specify versioned files with a regex field containing a named capture group called version:
[package]
versioned_files = [
"Cargo.toml",
{ path = "README.md", regex = 'version:\s+(?<version>\d+\.?\d+\.?\d+)' }
]This allows Knope to automatically update version numbers in documentation, installation instructions, and other text files that don't have a structured format.
config 0.3.0 (2025-11-03)
Breaking Changes
VersionedFile::TryFromnow returnsConfigErrorinstead ofUnknownFile
versioning 0.5.3 (2025-10-15)
Features
Add first-class Deno release support to Knope
- Detect Deno projects, workspaces, and nested packages so they can be released with Knope
- Reuse the deno_config and deno_lockfile crates to stay current with maintained Deno config and lockfile formats
- Extend release pipeline so Deno projects get version bumps and changelogs consistent with Node.js projects
- Updated Concept docs for Change, Changeset, Package
- Updated Reference docs for Packages and Default Config
- Add tests for deno based projects and workspaces
knope 0.21.4 (2025-10-15)
Features
Add first-class Deno release support to Knope
- Detect Deno projects, workspaces, and nested packages so they can be released with Knope
- Reuse the deno_config and deno_lockfile crates to stay current with maintained Deno config and lockfile formats
- Extend release pipeline so Deno projects get version bumps and changelogs consistent with Node.js projects
- Updated Concept docs for Change, Changeset, Package
- Updated Reference docs for Packages and Default Config
- Add tests for deno based projects and workspaces
versioning 0.5.2 (2025-08-16)
Fixes
Fix pre-release versioning when there are no previous stable versions
Previously, if there was not a Git tag containing a previous stable version, Knope would default to "0.0.0".
Because of the special 1.0.0 rules, this also meant there was no way to start a project at a pre-release of 1.0.0
with no prior releases.
Now, if there are no previous stable releases, Knope will use the version in your files instead of calculating a version
based on "0.0.0".
knope 0.21.3 (2025-08-16)
Fixes
Fix pre-release versioning when there are no previous stable versions
Previously, if there was not a Git tag containing a previous stable version, Knope would default to "0.0.0".
Because of the special 1.0.0 rules, this also meant there was no way to start a project at a pre-release of 1.0.0
with no prior releases.
Now, if there are no previous stable releases, Knope will use the version in your files instead of calculating a version
based on "0.0.0".
versioning 0.5.1 (2025-08-10)
Features
- Support
workspace.package.versionin Cargo.toml
versioning 0.5.0 (2025-08-10)
Breaking Changes
Changenow hassummaryanddetailsinstead ofdescriptionChangeno longer implsFrom<changesets::PackageChange>ChangeSourcevariants are now a struct style instead of tuple stylePackage::get_changeshas a completely different signature, to support providing commit info for each changeReleaseNoteshas new, requiredchange_templatesfield- Swapped
From<ChangeType>toFrom<&ChangeType>forchangesets::ChangeType
ReleaseNotes::create_release is no longer pub
This wasn't being used by Knope or Knope Bot directly, and non-pub functions give better lints.
If anyone is using this crate and needed that function, let me know!
Features
impl Default for ReleaseNotes