chore(deps): update dependency knope to v0.18.0 - autoclosed #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.16.2
->0.18.0
Release Notes
knope-dev/knope (knope)
v0.18.0
Breaking Changes
Auto-update Cargo workspace dependencies when using default config
If using the Cargo workspace default configuration,
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
inversioned_files
Dependencies within a
Cargo.lock
can now be updated.Support for dependencies within
Cargo.toml
Dependencies within a
Cargo.toml
file can now be updatedas 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 writtena 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 newdependency updating and lockfile support.
v0.17.0
Breaking Changes
Forge date now matches CHANGELOG date
If you prepare a release and generate a changelog Markdown file in one workflow, then create a forge release in a
separate workflow, the forge release date will now match the changelog date (if any). Previously, the forge release got
the current date (at the time of running the workflow).
Match scope-filtering behavior to docs
The docs state, in regard to a
package.scopes
config, "if not defined, Knope will consider all scopes."This is the intended behavior, but wasn't true until now. The actual behavior, for multi-package repos, was that if
any package had scopes defined, all would start filtering scopes.
This has been corrected, packages are now more independent in their scope filtering behavior.
Properly use case insensitivity when checking conventional commits
Per the conventional commits spec all units of a
conventional commit are case-insensitive.
Until now, Knope was treating commit footers and scopes as case-sensitive. This has been corrected, which may result
in different behavior for some projects.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.