-
-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
Lets say I have a workspace with two packages:
backendfrontend
And a manually created changeset file with some typos in the packages:
---
backenDD: patch
frontenDD: patch
---
# Initial commit
The knope PrepareRelease step will:
- not consume the changeset
- neither warn nor error out.
Expected behavior:
Error/warn saying that the changeset references an un-existing package.
Note:
We've created a changeset initially with knope document-change, then in response to a PullRequest comment renamed a package in Cargo.toml/knope.toml, but forgot to rename the package in the already created changeset file.
knope --version
knope 0.21.5
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels