Skip to content

release instructions: make clear what to do before signing the release candidate #342

@alexkli

Description

@alexkli

It's key to do at least these in the sources that will go into the release before starting the signing/build release process:

  • npm: release version in package.json
  • up to date CHANGELOG

But it's not very clear from the document... could be highlighted more.

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