Skip to content

chore: allow to deploy canary releases#284

Merged
gregberge merged 1 commit intomainfrom
canary-release
Apr 9, 2026
Merged

chore: allow to deploy canary releases#284
gregberge merged 1 commit intomainfrom
canary-release

Conversation

@gregberge
Copy link
Copy Markdown
Member

No description provided.

@gregberge gregberge requested review from a team, Copilot and jsfez and removed request for a team April 9, 2026 19:35
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
argos-js-sdk-reference Ready Ready Preview, Comment Apr 9, 2026 7:36pm

Request Review

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a manual release option to choose between a normal release and a canary release when running the Release workflow, enabling canary deployments via workflow_dispatch.

Changes:

  • Introduces a workflow_dispatch input release_type with normal and canary options.
  • Updates the publish step to conditionally run release vs release-canary based on the selected input.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gregberge gregberge merged commit 3431e7d into main Apr 9, 2026
69 checks passed
@gregberge gregberge deleted the canary-release branch April 9, 2026 20:04
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