Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo-workspace - package missing version header in changelog when only dependency is updated #2318

Closed
bukowa opened this issue Jun 20, 2024 · 1 comment · Fixed by #2320
Closed
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@bukowa
Copy link
Contributor

bukowa commented Jun 20, 2024

$ release-please --version
16.12.0

When package has only dependency update the changelog looks like this (both in CHANGELOG.md and pr body)
(note ck3oop-ui-rs: 0.0.1 missing version header`)

🤖 I have created a release beep boop

ck3oop-ui: 0.1.0

0.1.0 (2024-06-18)

Features

  • rust-core: Mod file parsing (03ce8e1)
ck3oop-core-rs: 0.1.0

0.1.0 (2024-06-18)

Features

  • rust-core: Mod file parsing (03ce8e1)
ck3oop-ui-rs: 0.0.1

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • ck3oop-core-rs bumped from 0.0.0 to 0.1.0

This PR was generated with Release Please. See documentation.

@bukowa bukowa added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jun 20, 2024
@bukowa
Copy link
Contributor Author

bukowa commented Jun 20, 2024

#1530
#2089
#2112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants