Skip to content

Consider new release workflow #551

@adamkudrna

Description

@adamkudrna

Possible replacement action for draft releasing:

https://github.com/marketplace/actions/publish-release

Problems to Fix

  • Get rid of release drafts and automated releasing?
  • ✅ Fix automatic tagging to include the v prefix on publish (drafting is fine). Can be possibly fixed by using another action?
  • Generate GH releases using the built-in GH feature? Or:
    • ✅ add PR author to each record within the existing workflow,
    • ✅ try to add the diff link (this can still be done manually).
  • Check Frontend Garden release management workflow where everything works fine. 🎉
  • Move from the EndBug/version-check action to gh release CLI command. — moved to Prefer gh release CLI over third-party actions where possible #555

GitHub CLI

# Publish a release that was previously a draft
$ gh release edit v1.2.3 --draft=false

eregon/publish-release#14 (comment)

cli/cli#5422

Other Maintained Actions

Metadata

Metadata

Assignees

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions