ci: publish @relaycast/engine in lockstep; remove publish-engine workflow by willwashburn · Pull Request #152 · AgentWorkforce/relaycast

willwashburn · 2026-06-01T04:11:18Z

Summary

Fold @relaycast/engine into the lockstep @relaycast/* publish so it's versioned and released with the rest of the packages, and remove the separate manual publish workflow.

publish-npm.yml: include engine in the version-bump sweep (drop the SKIP = new Set(['engine']) exclusion and the !== '@relaycast/engine' dependency-rewrite carve-out), and add engine to the publish matrix, the workflow_dispatch package options, and the summary table.
Delete publish-engine.yml (the independent, manually-dispatched engine publish).

Verified the version-sweep script now bumps @relaycast/engine and rewrites internal @relaycast/* deps for all packages; the three touched workflows parse as valid YAML.

Heads up: feat/engine-package also carries an equivalent change (14bdc34 "ci: fold engine publish into publish-npm workflow"). Whichever lands first, the other should drop its copy to avoid a conflict.

Context

This re-lands a change that briefly went directly to main (1ec80ab) by mistake while #151 was merging; that commit was reverted on main (e9e4651) and is re-submitted here for normal review.

🤖 Generated with Claude Code

…orkflow The engine is no longer versioned/released independently — fold it into the lockstep @relaycast/* publish: - publish-npm.yml: add `engine` to the version-bump sweep (drop the SKIP set and the `!== '@relaycast/engine'` dependency-rewrite exclusion) and to the publish matrix, dispatch options, and summary table. - Delete the custom publish-engine.yml workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

gemini-code-assist · 2026-06-01T04:11:21Z

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

coderabbitai · 2026-06-01T04:11:25Z

Warning

Review limit reached

@agent-relay-bot[bot], we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 12 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 756a8d2c-150a-4659-becc-ac0f87522b6a

📥 Commits

Reviewing files that changed from the base of the PR and between e9e4651 and 5f36d69.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

.github/workflows/publish-engine.yml
.github/workflows/publish-npm.yml
.trajectories/index.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch ci/engine-lockstep-publish

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

cubic-dev-ai

No issues found across 2 files

_{Re-trigger cubic}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 82a5b8ce7b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-06-01T04:12:40Z

          - all
          - a2a
          - types
+          - engine


Remove engine from single-package choices

When package: engine is selected, this workflow takes the publish-single path and publishes only packages/engine, but the build step now rewrites every @relaycast/* dependency to the new lockstep version. That means @relaycast/engine@NEW_VERSION is published with exact dependencies such as @relaycast/a2a@NEW_VERSION and @relaycast/types@NEW_VERSION that were not published by this run, making the engine package uninstallable unless those versions already happened to exist. Either keep engine out of single-package dispatch or make the engine option publish its lockstep dependencies too.

Useful? React with 👍 / 👎.

agent-relay-bot · 2026-06-01T04:17:39Z

Updated PR #152 locally.

Changes made:

Hardened .github/workflows/publish-npm.yml so custom_version and NEW_VERSION are passed through environment variables instead of interpolated into shell/inline JS.
Added @relaycast/engine to the generated release install snippet, matching the new lockstep package table.

Local checks:

npm ci
Workflow YAML parse and extracted version-step bash -n
Version step simulation in a temp copy confirmed all workspace versions and internal @relaycast/* deps sync, including engine
npx turbo build/test/lint --filter=@relaycast/engine
Non-dashboard serial test/lint pass succeeded
Full build reached the private Next dashboard and was killed with exit 137 in this container; package-level builds for affected/relevant packages passed directly.

agent-relay-bot

✅ pr-reviewer applied fixes — committed and pushed 2620f09 to this PR. The notes below describe what changed.

Updated PR #152 locally.

Changes made:

Hardened .github/workflows/publish-npm.yml so custom_version and NEW_VERSION are passed through environment variables instead of interpolated into shell/inline JS.
Added @relaycast/engine to the generated release install snippet, matching the new lockstep package table.

Local checks:

npm ci
Workflow YAML parse and extracted version-step bash -n
Version step simulation in a temp copy confirmed all workspace versions and internal @relaycast/* deps sync, including engine
npx turbo build/test/lint --filter=@relaycast/engine
Non-dashboard serial test/lint pass succeeded
Full build reached the private Next dashboard and was killed with exit 137 in this container; package-level builds for affected/relevant packages passed directly.

agent-relay-bot · 2026-06-01T04:17:47Z

✅ pr-reviewer applied fixes — committed and pushed 2620f09 to this PR. The notes below describe what changed.

Updated PR #152 locally.

Changes made:

Hardened .github/workflows/publish-npm.yml so custom_version and NEW_VERSION are passed through environment variables instead of interpolated into shell/inline JS.
Added @relaycast/engine to the generated release install snippet, matching the new lockstep package table.

Local checks:

npm ci
Workflow YAML parse and extracted version-step bash -n
Version step simulation in a temp copy confirmed all workspace versions and internal @relaycast/* deps sync, including engine
npx turbo build/test/lint --filter=@relaycast/engine
Non-dashboard serial test/lint pass succeeded
Full build reached the private Next dashboard and was killed with exit 137 in this container; package-level builds for affected/relevant packages passed directly.

agent-relay-bot · 2026-06-01T04:25:17Z

✅ pr-reviewer applied fixes — committed and pushed 5f36d69 to this PR. The notes below describe what changed.

Fixed the actionable review finding in .github/workflows/publish-npm.yml: engine is no longer a manual single-package publish option, but remains in the all publish matrix. That prevents publishing @relaycast/engine alone after lockstep dependency rewrites.

Local checks run:

npx prettier --check .github/workflows/publish-npm.yml
Node YAML/workflow shape check confirming engine absent from single choices and present in the all-package matrix
npx turbo build --filter=... for all public packages
npx turbo test --filter=... for all public packages
npx turbo lint --filter=@relaycast/engine

agent-relay-bot

✅ pr-reviewer applied fixes — committed and pushed 5f36d69 to this PR. The notes below describe what changed.

Fixed the actionable review finding in .github/workflows/publish-npm.yml: engine is no longer a manual single-package publish option, but remains in the all publish matrix. That prevents publishing @relaycast/engine alone after lockstep dependency rewrites.

Local checks run:

npx prettier --check .github/workflows/publish-npm.yml
Node YAML/workflow shape check confirming engine absent from single choices and present in the all-package matrix
npx turbo build --filter=... for all public packages
npx turbo test --filter=... for all public packages
npx turbo lint --filter=@relaycast/engine

cubic-dev-ai Bot reviewed Jun 1, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Jun 1, 2026

View reviewed changes

chore: apply pr-reviewer fixes for #152

2620f09

agent-relay-bot Bot reviewed Jun 1, 2026

View reviewed changes

chore: apply pr-reviewer fixes for #152

5f36d69

agent-relay-bot Bot reviewed Jun 1, 2026

View reviewed changes

willwashburn merged commit 8e167e5 into main Jun 1, 2026
5 checks passed

willwashburn deleted the ci/engine-lockstep-publish branch June 1, 2026 16:53

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ci: publish @relaycast/engine in lockstep; remove publish-engine workflow#152

ci: publish @relaycast/engine in lockstep; remove publish-engine workflow#152
willwashburn merged 3 commits into
mainfrom
ci/engine-lockstep-publish

willwashburn commented Jun 1, 2026

Uh oh!

gemini-code-assist Bot commented Jun 1, 2026

Uh oh!

coderabbitai Bot commented Jun 1, 2026 •

edited

Loading

Review limit reached

Uh oh!

cubic-dev-ai Bot left a comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Jun 1, 2026

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot left a comment

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

willwashburn commented Jun 1, 2026

Summary

Context

Uh oh!

gemini-code-assist Bot commented Jun 1, 2026

Uh oh!

coderabbitai Bot commented Jun 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jun 1, 2026

Choose a reason for hiding this comment

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot left a comment

Choose a reason for hiding this comment

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot commented Jun 1, 2026

Uh oh!

agent-relay-bot Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

coderabbitai Bot commented Jun 1, 2026 •

edited

Loading