Skip to content

Generalize first publish selection#53

Closed
aretw0 wants to merge 1 commit into
mainfrom
develop
Closed

Generalize first publish selection#53
aretw0 wants to merge 1 commit into
mainfrom
develop

Conversation

@aretw0

@aretw0 aretw0 commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • rename the first-publish workflow from vault-seed-specific to selection-driven
  • add generic release:first-publish scripts while keeping vault-seed aliases for this handoff
  • update readiness/docs/tests to use --selection vault-seed-ready instead of product-coupled script names

Validation

  • node --test scripts/ci/test-first-publish-selection.mjs scripts/ci/test-deploy-publish-workflows.mjs scripts/ci/test-release-readiness.mjs scripts/ci/test-distribution-status-doc.mjs
  • pnpm --silent run release:first-publish:plan -- --selection vault-seed-ready --json
  • pnpm --silent run release:first-publish -- --selection vault-seed-ready --plan --json
  • pnpm --silent run release:first-publish:check -- --selection vault-seed-ready
  • refarm agent finish --lane after-edit --run --json
  • refarm agent finish --lane after-commit --run --json

@aretw0 aretw0 closed this Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant