Skip to content

ci(publish): add @relayauth/migrate to the publish workflow#31

Merged
khaliqgant merged 1 commit intomainfrom
ci/publish-migrate-package
Apr 23, 2026
Merged

ci(publish): add @relayauth/migrate to the publish workflow#31
khaliqgant merged 1 commit intomainfrom
ci/publish-migrate-package

Conversation

@khaliqgant
Copy link
Copy Markdown
Member

@khaliqgant khaliqgant commented Apr 23, 2026

Summary

#26 introduced `@relayauth/migrate` as a workspace package but didn't update `publish.yml`. Today a `workflow_dispatch` with `package=all` skips it, and once you try to publish a new `@relayauth/server` it'll fail downstream because `server`'s dep on `@relayauth/migrate: "*"` can't resolve when migrate isn't on npm.

Changes

  • Added `migrate` to the `package` dropdown.
  • Inserted `migrate` into the `all` ordering before `server`. The publish job runs `max-parallel: 1`, so list order == publish order — and server depends on migrate, so migrate has to land first.

Everything else generalizes: the "Resolve package directory" step falls through to the default branch for `migrate` (which is `packages/migrate/`, no special-casing needed), and the version-bump loop already iterates over `$PACKAGES` generically.

Test plan

  • `workflow_dispatch` with `dry_run: true`, `package: migrate`, `version: patch` — the dry-run publish step produces a tarball without errors.
  • `workflow_dispatch` with `dry_run: true`, `package: all` — six dry-run publishes succeed in order: types → core → sdk → migrate → server → relayauth.

Unblocks

  • AgentWorkforce/cloud#313 — needs `@relayauth/migrate` on npm to consume the runner.

🤖 Generated with Claude Code


Open in Devin Review

Package was introduced in #26 but the publish workflow's choice list
and 'all' branch were never updated, so a workflow_dispatch with
package=all would skip it and subsequent @relayauth/server@<new>
publishes would fail downstream — server's dependency on
@relayauth/migrate can't resolve when migrate isn't on npm.

Inserted before server in the 'all' ordering because the publish job
runs max-parallel: 1 and server depends on migrate; list order is
publish order. The generic package-directory resolver in the publish
step already handles packages/migrate/ via the default branch — no
other changes needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@khaliqgant khaliqgant merged commit d8ffd8e into main Apr 23, 2026
2 checks passed
@khaliqgant khaliqgant deleted the ci/publish-migrate-package branch April 23, 2026 19:20
Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

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