Skip to content

Configure semantic-release #36

@ericcrosson-bitgo

Description

@ericcrosson-bitgo

Every merge to master should invoke semantic-release, which will publish a package version to npm if appropriate.

Eventually we will add changelog maintenance to semantic-release via a plugin, but this has been cut from initial scope due to the complexity that our gpg-commit-signing requirement adds.

Remember that before we invoke semantic release, we need to tag our projects manually to set the initial version. Otherwise semantic-release will default to 1.0.0 for the initial version, which we would avoid if possible since we are in an alpha state.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions