Skip to content

Tags: knope-dev/knope

Tags

knope/v0.18.1

Toggle knope/v0.18.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release packages (#1191)

> [!IMPORTANT]
> Merging this pull request will create these releases

# config 0.2.0 (2024-09-15)
## Breaking Changes

- Changed type of `Package::assets` to `Assets` enum
# knope 0.18.1 (2024-09-15)
## Features

### Support glob patterns for package assets

You can now provide a glob pattern when defining package assets instead
of specifying each file individually in a list.
This is especially useful when your asset names are dynamic (containing
a version, date, or hash, for example) or
when different releases have different assets.

Knope will _not_ error if the glob pattern doesn't match any files.
You can't combine glob patterns with individual file names.

```toml
[package]
assets = "assets/*"
```

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

config/v0.2.0

Toggle config/v0.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release packages (#1191)

> [!IMPORTANT]
> Merging this pull request will create these releases

# config 0.2.0 (2024-09-15)
## Breaking Changes

- Changed type of `Package::assets` to `Assets` enum
# knope 0.18.1 (2024-09-15)
## Features

### Support glob patterns for package assets

You can now provide a glob pattern when defining package assets instead
of specifying each file individually in a list.
This is especially useful when your asset names are dynamic (containing
a version, date, or hash, for example) or
when different releases have different assets.

Knope will _not_ error if the glob pattern doesn't match any files.
You can't combine glob patterns with individual file names.

```toml
[package]
assets = "assets/*"
```

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

versioning/v0.3.0

Toggle versioning/v0.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release packages (#1170)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.3.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).
# config 0.1.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.
# knope 0.18.0 (2024-08-18)
## Breaking Changes

### Auto-update Cargo workspace dependencies when using default config

If using the Cargo workspace [default
configuration](https://knope.tech/reference/default-config/#cargo-workspaces),
Knope will now attempt to automatically update the version of workspace
members in dependencies _and_ the workspace `Cargo.lock`.

To avoid this, use `knope --generate` to create a manual config file and
customize the behavior.

### Don't create _any_ go module tags that match package names

Knope already avoided creating duplicate tags for Go modules which match
tags that would be created by the `Release` step for the package.
Now, Knope won't create a Go module tag if it matches a release tag for
_any_ configured package, to avoid potential conflicts.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Fixes

### Deduplicate release actions

Knope now collects all actions to be performed across all packages and
runs them at once with deduplication.

This means that if multiple packages write to the same `versioned_file`,
for example, the file will only be written
a single time.
Changesets will also only be deleted once, files will be staged to Git
only once, etc.

This mostly only impacts the output during `--dry-run` or `--verbose`,
but is especially important for the new
dependency updating and lockfile support.

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

knope/v0.18.0

Toggle knope/v0.18.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release packages (#1170)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.3.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).
# config 0.1.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.
# knope 0.18.0 (2024-08-18)
## Breaking Changes

### Auto-update Cargo workspace dependencies when using default config

If using the Cargo workspace [default
configuration](https://knope.tech/reference/default-config/#cargo-workspaces),
Knope will now attempt to automatically update the version of workspace
members in dependencies _and_ the workspace `Cargo.lock`.

To avoid this, use `knope --generate` to create a manual config file and
customize the behavior.

### Don't create _any_ go module tags that match package names

Knope already avoided creating duplicate tags for Go modules which match
tags that would be created by the `Release` step for the package.
Now, Knope won't create a Go module tag if it matches a release tag for
_any_ configured package, to avoid potential conflicts.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Fixes

### Deduplicate release actions

Knope now collects all actions to be performed across all packages and
runs them at once with deduplication.

This means that if multiple packages write to the same `versioned_file`,
for example, the file will only be written
a single time.
Changesets will also only be deleted once, files will be staged to Git
only once, etc.

This mostly only impacts the output during `--dry-run` or `--verbose`,
but is especially important for the new
dependency updating and lockfile support.

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

config/v0.1.0

Toggle config/v0.1.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release packages (#1170)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.3.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).
# config 0.1.0 (2024-08-18)
## Breaking Changes

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.
# knope 0.18.0 (2024-08-18)
## Breaking Changes

### Auto-update Cargo workspace dependencies when using default config

If using the Cargo workspace [default
configuration](https://knope.tech/reference/default-config/#cargo-workspaces),
Knope will now attempt to automatically update the version of workspace
members in dependencies _and_ the workspace `Cargo.lock`.

To avoid this, use `knope --generate` to create a manual config file and
customize the behavior.

### Don't create _any_ go module tags that match package names

Knope already avoided creating duplicate tags for Go modules which match
tags that would be created by the `Release` step for the package.
Now, Knope won't create a Go module tag if it matches a release tag for
_any_ configured package, to avoid potential conflicts.

## Features

### Support for `Cargo.lock` in `versioned_files`

Dependencies within a `Cargo.lock` [can now be
updated](https://knope.tech/reference/config-file/packages#cargolock).

### Support for dependencies within `Cargo.toml`

Dependencies within a `Cargo.toml` file [can now be
updated](https://knope.tech/reference/config-file/packages/)
as part of `versioned_files`.

## Fixes

### Deduplicate release actions

Knope now collects all actions to be performed across all packages and
runs them at once with deduplication.

This means that if multiple packages write to the same `versioned_file`,
for example, the file will only be written
a single time.
Changesets will also only be deleted once, files will be staged to Git
only once, etc.

This mostly only impacts the output during `--dry-run` or `--verbose`,
but is especially important for the new
dependency updating and lockfile support.

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>

versioning/v0.2.0

Toggle versioning/v0.2.0's commit message

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
Release packages (#1151)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.2.0 (2024-08-10)
## Breaking Changes

- Move HeaderLevel to internal, parse with Changelog::new

## Features

- `impl From<ReleaseTag> for String`

---------

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>
Co-authored-by: Dylan Anthony <[email protected]>

knope/v0.17.1

Toggle knope/v0.17.1's commit message

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
Release packages (#1151)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.2.0 (2024-08-10)
## Breaking Changes

- Move HeaderLevel to internal, parse with Changelog::new

## Features

- `impl From<ReleaseTag> for String`

---------

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>
Co-authored-by: Dylan Anthony <[email protected]>

config/v0.0.2

Toggle config/v0.0.2's commit message

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
Release packages (#1151)

> [!IMPORTANT]
> Merging this pull request will create these releases

# versioning 0.2.0 (2024-08-10)
## Breaking Changes

- Move HeaderLevel to internal, parse with Changelog::new

## Features

- `impl From<ReleaseTag> for String`

---------

Co-authored-by: knope-bot-test[bot] <150975753+knope-bot-test[bot]@users.noreply.github.com>
Co-authored-by: Dylan Anthony <[email protected]>

versioning/v0.1.0

Toggle versioning/v0.1.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: prepare releases (#1132)

This PR was created by Knope. Merging it will create a new release

---------

Co-authored-by: GitHub <[email protected]>
Co-authored-by: Dylan Anthony <[email protected]>

knope/v0.17.0

Toggle knope/v0.17.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: prepare releases (#1132)

This PR was created by Knope. Merging it will create a new release

---------

Co-authored-by: GitHub <[email protected]>
Co-authored-by: Dylan Anthony <[email protected]>