Skip to content

Automate release publishing end-to-end #551

@0xisk

Description

@0xisk

🧐 Motivation

The release flow is mostly manual and brittle. Cutting v0.1.0 required manually creating the GitHub Release/tag, and a failed build meant manually deleting and recreating the tag/release to retry. We should automate it so a release is a single deterministic action.

📝 Details

Automate so that merging the version-bump PR to main (from a release-v* branch) drives the rest:

  • Auto-create the GitHub Release + tag v<version> from contracts/package.json on merge, which fires the existing release.yml publish job. No manual release creation.
  • Make retries safe/idempotent (re-running shouldn't need manual tag deletion).

Out of scope / tracked separately:

✅ Acceptance

  • Merging a release-v* bump publishes to npm with no manual GitHub UI steps.
  • A failed publish can be retried without manual tag/release surgery.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

Status
Backlog

Relationships

None yet

Development

No branches or pull requests

Issue actions