Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Generate changelogs without bumping version

See original GitHub issue

Affected Packages

cli

Problem

We’re using a workflow where every (sub)-package in our monorepo utilizes the same version. I thought linked: [['*']] would cause it to link every package together (similar to how lerna’s versioning locks it), however, this doesn’t seem to work reliably / at all 🤔 (ref https://github.com/atlassian/changesets/issues/570).

The next best thing would be to only rely on changesets for generating the changelogs, and keep doing the versioning/publishing externally, which seems to be hinted at in the docs, but any real info around this subject is missing (as per https://github.com/atlassian/changesets/issues/593).

Proposed solution

Would be ideal to have a dedicated changeset generate or changeset prepare command

Issue Analytics

State:
Created 2 years ago
Reactions:7
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

Andaristcommented, Dec 17, 2021

@fivethreeo isn’t the fixed mode that is being implemented here solving your problem? I’m not sure how this is relevant to this thread - unless I’m totally misunderstanding what you are asking for here

0reactions

fivethreeocommented, Dec 17, 2021

Look over all packages, collect changesets, find highest bump type, update those changesets with the bump type and add a changeset to any packages that don’t have one with a «bumped versions» message