Skip to content

Deploy without fetch - #1581

Merged
josephjclark merged 2 commits into
release/nextfrom
deploy-without-fetch
Oct 13, 2026
Merged

josephjclark merged 2 commits into
release/nextfrom
deploy-without-fetch

Conversation

@josephjclark

@josephjclark josephjclark commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

When deploying a project, the CLI currently errors if a statefile isn't available locally.

This PR fixes two issues:

  1. When deploying with a UUID, if we don't have a local state file, run a fetch first.
  2. (unrelated really) If running deploy --no-checkout, the CLI today will NOT write a state file for the deployed project. That's an error.

Fixes #1303

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

@josephjclark
josephjclark marked this pull request as ready for review October 9, 2026 14:20
Comment thread packages/cli/src/projects/deploy.ts
Base automatically changed from release/next to main October 12, 2026 13:11
@josephjclark
josephjclark changed the base branch from main to release/next October 12, 2026 13:13
@josephjclark
josephjclark deleted the branch release/next October 13, 2026 08:34
@github-project-automation github-project-automation Bot moved this from New Issues to Done in Core Oct 13, 2026
@josephjclark josephjclark reopened this Oct 13, 2026
@josephjclark
josephjclark merged commit b29758d into release/next Oct 13, 2026
11 checks passed
@josephjclark
josephjclark deleted the deploy-without-fetch branch October 13, 2026 09:05
josephjclark added a commit that referenced this pull request Oct 13, 2026
* [rebased] Support workflow aliases via folder names- #1579 (#1585)

* Support workflow aliases via folder names

A workflow's folder name in the workspace now acts as a local alias when
it differs from the workflow id. Aliases can be used to look up
workflows, are preserved across checkout and pull, and are never
deployed. Aliases that clash with another workflow's id or alias are
dropped with a warning.

* Show workflow aliases in project list

Aliases are folder names, so they only exist on the checked-out
project. List them next to the workflow ids of the active project so
users can see which short names are available.

* Split workflow lookup into getWorkflow and findWorkflow

getWorkflow matched on id, alias, name and uuid, so id-based callers
(diff, merge, checkout) could resolve an alias to the wrong workflow.
It now matches ids only. findWorkflow handles user input and throws
when more than one workflow matches.

---------

Co-authored-by: Frank Midigo <midigofrank@gmail.com>

* Deploy without fetch (#1581)

* auto-fetch state file

* changeset

* Better execute output (#1584)

* better default output

* changeset

* fix tests

* versions

---------

Co-authored-by: Frank Midigo <midigofrank@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants