Repository navigation
feat: create releases without promoting a channel - #948
Merged
Merged
Conversation
|
Enclave skipped this draft pull request. It will run automatically when you mark the PR as Ready for review. |
alongubkin
marked this pull request as ready for review
October 8, 2026 11:28
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds create-only releases to Alien.
SDKs and the CLI stay versioned as today.
User flow: You want to release normally
No changes needed.
alien releasestill advancesproduction;--channel stagingstill advances staging.User flow: You want to publish now and deploy later
alien release --no-promote --title "Fix checkout"This saves a release without changing a channel or scheduling deployment updates. The output includes its ID and the command to promote it later.
You can also use Promote this exact release in the dashboard.
User flow: You want to reuse your CI build
Download the successful CI build's
.alienartifact, then run:alien release --prebuilt --no-promote --title "Fix checkout"No application rebuild is needed. Local image artifacts are pushed; existing remote image URIs are reused. Promotion later uses the saved release, even if the branch has advanced.
User flow: You want an urgent production fix
Create the release with
--no-promote, inspect it, then promote its ID directly toproduction. Staging is optional.How we tested this locally
Ran the built CLI against a local HTTP API and PostgreSQL using the test platform: create-only left production, staging, deployment rows, and update queues unchanged.
Published a newer release, then promoted the original ID: only its production deployment was queued. The saved CI artifact was unchanged, and
--titlepersisted.Repeated create-only through the CLI's stackless path; channels and update queues stayed unchanged.
Executed both printed promotion commands with a differently linked project and conflicting project/workspace/server defaults. Each command promoted only the selected project.
This checks release creation and scheduling, not a cloud rollout.
promote: falseis sent andchannelis omitted.--no-promoteworks with the default arguments, rejects an explicit--channel, and rejects manager mode before any network or build work.falseand omitted defaults.cargo check -p alien-cli, the executable build, release-command tests, and Rust/TypeScript CI pass. The changed Rust file passes formatting checks.Client artifacts were regenerated with
generate:api-copy-openapiandgenerate:api-platform-sdk. TypeScript package CI passes, including the generated SDK build. A separate local full-SDK rebuild exceeded the Node heap limit; request serialization was checked locally. Server support must be deployed before this CLI is published.