Skip to content

Track shared release workflow from main #32

Description

@Teakowa

Goal

Make WrightKit crate consumers follow the shared release workflow directly from wrightkit/.github@main so routine shared-workflow maintenance does not require synchronized consumer pin updates.

Context

The shared release workflow is an internal WrightKit CI contract. Immutable consumer SHAs add operational coupling: every squash merge in wrightkit/.github requires follow-up PRs in each consumer, and using a pre-merge PR head SHA can leave consumers pointing at a non-durable revision.

External release tooling remains pinned inside the shared workflow; this change only removes immutable pinning between WrightKit-owned repositories.

Scope

  • Change current consumers of .github/workflows/release-plz-crates.yml to reference @main.
  • Apply the policy consistently to opy-rs, workshop-rs, and deltin-rs.
  • Keep consumer permissions, secrets, triggers, and release-plz policy unchanged.
  • Keep external Action and release-plz CLI version pinning owned by wrightkit/.github.

Non-goals

  • Change release versioning, changelog, or publication policy.
  • Change the shared workflow implementation.
  • Add release automation to repositories that do not currently consume it.

Acceptance criteria

  • opy-rs, workshop-rs, and deltin-rs use wrightkit/.github/.github/workflows/release-plz-crates.yml@main.
  • Consumer release workflows otherwise remain unchanged.
  • A post-merge release run resolves the shared workflow from wrightkit/.github main and creates the expected release/release-pr jobs.
  • Already-published packages remain a safe no-op.

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