Skip to content

Consider changing versioning strategy #3748

@paulmillr

Description

@paulmillr

All packages currently have different versioning scheme. Here's a couple thoughts how can this be improved:

a. Adopt one double-digit version for all packages e.g. v10.
b. Use year as version. "2024" can be shortened to just v24. That would automatically make v25 breaking. Makes easier to understand which hardfork the particular version supports just by its year

Benefits of using the same number:

  1. Easier bug tracking / user reporting / dev UX. E.g. "We're on version 11, this happens" instead of "We're on version 4.4.0 with vm 0.10.2, this happens".
  2. Makes it easier to continue developing monorepo and reason about changes

Current package versions

"5.3.0"
"7.3.0"
"0.10.2"
"4.4.0"
"6.1.3"
"3.0.4"
"3.1.0"
"0.2.3"
"6.2.2"
"5.0.2"
"2.4.0"
"5.4.0"
"9.1.0"
"0.1.0"
"8.1.0"
"2.0.4"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions