Skip to content

Define rules for major, minor, patch version bumps #1732

@tidoust

Description

@tidoust

Via #1727 (comment)

Documentation does not say anything about version bumps. It would be useful to clarify and document the rules we follow:

  • Major bumps: a backward-incompatible schema, API, or guarantee change.
  • Minor bumps: a backward-compatible schema, API, or guarantee change. Also, we currently do a minor bump when a spec gets added/deleted from the resulting package. That latter rule may make less sense in the "consolidated" packages @webref/events and now @webref/css (although if we add back extracts per spec in @webref/css, perhaps we should keep following that rule?).
  • Patch bumps: data updates.

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