You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(deps): update dependency knope to v0.18.0 (#1099)
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| [knope](https://knope.tech)
([source](https://togithub.com/knope-dev/knope)) | minor | `0.17.0` ->
`0.18.0` |
---
### Release Notes
<details>
<summary>knope-dev/knope (knope)</summary>
###
[`v0.18.0`](https://togithub.com/knope-dev/knope/blob/HEAD/CHANGELOG.md#0180-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.
</details>
---
### 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View the
[repository job
log](https://developer.mend.io/github/openapi-generators/openapi-python-client).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4yNi4xIiwidXBkYXRlZEluVmVyIjoiMzguMjYuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
0 commit comments