release-please changelog only include actual package changes

Open
  • Is something wrong?
#24 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, rust
Domain
release

Research direction

Start by reviewing the repository’s release configuration and package changelog setup to see how release-please currently gathers changes; the issue does not name specific files. Compare that behavior with the proposed changesets or covector approaches, including their release PR tradeoffs. Done means each package changelog lists only that package’s changes, with the release PR behavior chosen and documented.

Written by the indexing model from the issue text.

Description

Currently, the changelogs in all the packages end up being identical - including all changes.

I suspect the most straightforward way around this is to use changesets. One potential might need a migration to https://github.com/jbolda/covector

Considerations:

  • release-please keeps every app release in separate PR
  • covector keeps changelogs separate, but creates one release PR
Dominant language
Rust
Stars
0
Forks
3
Avg merge
1d 13h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.