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.

Questions about prerelease versions and independent mode

See original GitHub issue

Hi,

this project looks very interesting and I’m evaluating if I can try it out to some of our monorepositories.

I have two questions first, which I couldn’t find any answer in the docs.

The prerelease feature changes the version by appending the tag name. Is there a way to specify the npm dist-tag but keep the version as-is? In our case when we create a release we publish to next dist-tag by default. Then when we want to promote the version to latest, we do so by running a script manually that assigns the version to latest. However, the version does not change from next to latest, only the dist-tag. We also have canary releases, in which case the current implementation of a prerelease would work, as the version should change as well.
Is “independent” mode the only available mode? In Lerna there are 2 modes: locked and independent. In our case we use locked mode. I don’t see a big issue if we change to independent mode as a result of moving to changesets. I just want to understand if this is the only way or if there is another “hidden” option or something.

Thanks in advance, any feedback would be appreciated.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:10 (9 by maintainers)

Top GitHub Comments

1reaction

Andaristcommented, May 11, 2020

I noticed that private packages also get a changelog, but only if the bumped version is within the dependencies, not the dev dependencies.

I think the same happens for public packages. Updating dev dep shouldn’t affect the production release, that’s why dev deps do not bump versions.

What I expected instead is that private packages do not get a changelog, only the versions bump.

Currently, it is not possible to bump the version without also changing the changelog (at least I don’t think it is possible). A (somewhat) related comment/discussion about versioning private packages: https://github.com/atlassian/changesets/issues/339#issuecomment-619334412

0reactions

emmenkocommented, Jun 29, 2020

I guess this can be closed now. I’ve been using changesets across different repos for some time now and pretty much are use cases / requirements have been covered now. We’re very happy with that! Thanks 🙏

Top Results From Across the Web

'changeset version' fails if there is package without ... - GitHub

If there are packages without 'version' field changeset version fails with ... Questions about prerelease versions and independent mode #356.

Questions about software versioning

1. How should be the version of a software released for the first time? · 2. In case of an independent developer what...

Release Workflow | Yarn - Package Manager

An in-depth guide to Yarn's release workflow which helps with managing versions across a monorepo.

Untitled

Works in both normal and independent modes. If you have any packages with a prerelease version number (e.g. `2.0.0-beta.3`) and you run `lerna...

Potential Bug Fixes in R2023a Prerelease - MATLAB & Simulink

Product Record Bug Summary Deep Learning Toolbox 2803451 Image generation experiment template errors MATLAB 2736745 Security Issue: who ‑file might execute code MATLAB 2739217 tab completion...