Skip to content

Automate releases #20

@masklinn

Description

@masklinn

Useful as reference to external packagers, cf #19

There are a bunch of ways this could be handled tag first or bump first or have a workflow handle both (q: can a release be gated on various checks?)

  • cargo semver-checks to check for correctness of new version
  • create release / tags, may need multiple when cutting release as there are multiple crates / packages
  • publish crates
  • wheels release may need to be called as a sub-workflow? Or release triggered?

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