Skip to content

Publish the final Server candidate against Workflow 2.0.0-rc.55 #62

Description

@rmcdaniel

Objective

Publish one Server release candidate that consumes the qualified Workflow 2.0.0-rc.55 package and becomes the exact Server input for the final 2.0 conformance cycle.

Current evidence

  • Workflow 2.0.0-rc.55 is installable from Packagist and points to source commit 720512eefa0a5a97afeb410797cff8803ec76864.
  • A preserved Server worktree already contains the dependency, release-metadata, Docker, Helm, and affected sequence-assertion changes.
  • Focused child-workflow resume and exact Composer provenance checks passed locally.

Acceptance criteria

  • Server source and lockfile pin Workflow 2.0.0-rc.55 at the published source identity.
  • Server, Docker, and Helm release metadata agree on the next Server candidate version.
  • Resume-sequence assertions describe the current protocol contract rather than a stale fixture sequence.
  • Focused tests and the normal Server GitHub Actions suite pass on the pull request.
  • Repository-owned GitHub Actions publish the candidate image and release artifacts.
  • The published image reports the exact Workflow provenance and is used by the fixed final conformance tuple.

Stable 2.0.0 is explicitly out of scope for this issue and remains a separate human authorization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    authority:githubGitHub is the authoritative lifecycle record for this workcompletion:evidence-verifiedAcceptance, fixed version, and required operational evidence are publicly verifiedkind:release-blockerA release cannot proceed until this issue is resolvedpriority:P0Immediate release or data-integrity riskrepo:serverOwned by the standalone server repositorystatus:doneDerived from the authoritative closed issue state

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions