Skip to content

No warning/error on referenced but un-existing package #1756

@t-moe

Description

@t-moe

Lets say I have a workspace with two packages:

  • backend
  • frontend

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions