Skip to content

Package versioning #32

Description

@WardBenjamin

Right now, the library version is 1.0.0-alpha39. What's the reasoning behind having a semantic versioning format (v1.0.0) as well as the additional version indication?

Going forward, I'd like to stick to strict SemVer if possible, and everyone agrees that we should move towards that option:

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions