Skip to content

🐛 BUG: Pre-release version numbers should comply with semver #3555

@aaronadamsCA

Description

@aaronadamsCA

Which Cloudflare product(s) does this pertain to?

Wrangler

What version of Wrangler are you using?

3.1.1

What operating system are you using?

Ubuntu

Describe the Bug

Pre-release version numbers should correctly use semantic versioning. https://semver.org/

Here is an excerpt from this package's NPM version history:

image

According to semver, this is the precedence of these 4 versions:

0.0.0-33762441 < 0.0.0-436f752d < 0.0.0-528cc0fc < 3.1.1

This is confusing our package managers (for us, both pnpm and Renovate) in two ways:

  • 0.0.0-528cc0fc can upgrade to 3.1.1. This is actually a downgrade.
    • You can solve this by using a correct version number for pre-release builds.
  • 0.0.0-436f752d can upgrade to 0.0.0-528cc0fc. This is actually a downgrade.
    • You can solve this by using build identifiers properly, e.g. 3.2.0-beta+528cc0fc.
    • You can alternatively start using pre-release identifiers properly, e.g. 3.2.0-beta.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions