You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it does not work. Renovate bot did not create any updating PR.
On the other hand, the swc is working, and the renovate bot created PR like this:
fix(deps): update dependency @swc/core to ^1.5.3-nightly-20240501.1
The current version of swc@latest is 1.5.2. And the 1.5.3-nightly-20240501.1 is a pre-release version that Renovate would think newer than the latest version.
However, @rspack/core uses the same major, minor, and patch versions as latest for nightly and canary npm dist-tag.
When major, minor, and patch are equal, a pre-release version has lower precedence than a normal version:
What problem does this feature solve?
I'm trying to use Renovate to upgrade
@rspack/core
tonightly
for testing. Therenovate.json
looks like this:But it does not work. Renovate bot did not create any updating PR.
On the other hand, the
swc
is working, and the renovate bot created PR like this:The current version of
swc@latest
is1.5.2
. And the1.5.3-nightly-20240501.1
is a pre-release version that Renovate would think newer than the latest version.However,
@rspack/core
uses the same major, minor, and patch versions aslatest
fornightly
andcanary
npm dist-tag.This makes Renovate not updating the
@rspack/core
to latest(in my case,0.6.3
to0.6.3-canary-42527c5-20240504004548
)What does the proposed API of configuration look like?
Release
canary
andnightly
versions with a patch or minor version bump.E.g.: the
latest
of@rspack/core
is0.6.3
.Then, the
canary
version should be0.7.0-canary-{commit}-{datetime}
or0.6.4-canary-{commit}-{datetime}
if only patch changes exist.This is how typescript and changesets do the versioning.
The text was updated successfully, but these errors were encountered: