Skip to content

Improve release publishing workflow #162

Open
@phlax

Description

@phlax

Currently we manually create releases and any package that is not marked -dev in its VERSION file gets published

This creates a lot of unwanted commits, and boilerplate tasks that are pretty annoying and potentially unnecessary.

One possible solution is to make it such that:

  • When a PR lands on main if the -dev version has changed for one or more packages...
  • CI creates a branch for a new release, updates the VERSION files and publishes the packages to the version indicated by the previous dev version/s

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions