Manage Releases with changenote

Inspect the Repository

• Read the target repository's instructions, release documentation, .changenote/config.json, pending notes, and configured version files.
• Run commands from the target repository root, or pass --root PATH to the CLI.
• Use uvx changenote <command> as the default invocation; no separate CLI installation is needed.
• If the repository specifies another invocation, follow it.
• In the changenote source repository, use cargo run --locked -p changenote -- <command> to run the local implementation.
• Do not assume a consumer repository has the changenote Cargo package.
• If configuration is missing, initialize it only when setup is in scope and the package name and initial stable version are known.

uvx changenote init --name pkg-a --version 0.0.0

For a monorepo, configure explicit package names, repository-relative package paths, and package-relative version-file paths in .changenote/config.json. Each package directory must exist and contain a stable SemVer version file. Do not replace an existing configuration to add a note.