Skip to content

feat: deploy builds to channels server-side and support multiple channels - #210

Closed
robingenz wants to merge 1 commit into
mainfrom
feat/multi-channel-build-deploy
Closed

feat: deploy builds to channels server-side and support multiple channels#210
robingenz wants to merge 1 commit into
mainfrom
feat/multi-channel-build-deploy

Conversation

@robingenz

Copy link
Copy Markdown
Member

What

  • apps builds create --channel is now repeatable and comma-separated, and is sent as appChannelNames on build creation — the server deploys to the channels once the build succeeds, instead of the CLI creating the deployment client-side after waiting.
  • --detached can now be combined with --channel (the deploy no longer requires the CLI to wait); the conflict remains for --destination, which still deploys client-side.
  • Existing validations kept: --channel is web-only and mutually exclusive with --destination.

Requires capawesome-team/cloud-api-worker#793 (deploy the API first).

🤖 Generated with Claude Code

…nels

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings August 31, 2026 10:59

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the apps builds create command to support deploying builds to one or more channels server-side by sending appChannelNames at build creation time, eliminating the CLI’s previous client-side “wait then deploy-to-channel” flow and allowing --channel to be used with --detached.

Changes:

  • Extend build creation DTO to include appChannelNames.
  • Change --channel to be repeatable/comma-separated, parse it into a list, and send it as appChannelNames when creating builds (web-only), while keeping --channel mutually exclusive with --destination.
  • Remove client-side channel deployment creation (still create deployments client-side for --destination) and add tests for channel parsing/forwarding and updated --detached validation.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
src/types/app-build.ts Adds appChannelNames?: string[] to the build creation DTO.
src/commands/apps/builds/create.ts Parses multi-channel input, forwards appChannelNames, relaxes --detached vs --channel, and removes client-side channel deployment creation.
src/commands/apps/builds/create.test.ts Adds coverage for appChannelNames forwarding, comma-splitting, and updated detached/destination validation.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/commands/apps/builds/create.ts
@robingenz

Copy link
Copy Markdown
Member Author

Closed as not planned for now

@robingenz robingenz closed this Aug 31, 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.

2 participants