Skip to content

[Fix] Sync upstream 4.x (branch change under modern deployment) - #5

Merged
AbdullatifCengiz merged 3 commits into
4.xfrom
fatlat/sync-upstream
Oct 7, 2026
Merged

AbdullatifCengiz merged 3 commits into
4.xfrom
fatlat/sync-upstream

Conversation

@AbdullatifCengiz

Copy link
Copy Markdown

Brings in vitodeploy#1263 (changing a site's branch no longer checks out the live release under modern deployment) and vitodeploy#1271 (docs).

🤖 Generated with Claude Code

https://claude.ai/code/session_01ErQwQQUZfaxvDvWaVGBoe4


Generated by Claude Code

shawnhooper and others added 3 commits October 5, 2026 19:54
…under modern deployment (vitodeploy#1263)

With modern deployment enabled, a site's path is `<base>/current`, which
points at the active release. UpdateBranch ran `git fetch origin` and
`git checkout -f <branch>` in that path, so saving a new branch swapped
the code of the live release in place, with no build, no pre-flight and
no migrations. The forced checkout also restored tracked files over the
shared resources, replacing the `storage` symlink with a plain directory
in that release.

The branch is now switched in `<base>/source`, the checkout that holds
the shared resources and is pulled on every deployment. The next
deployment clones the new branch into a fresh release as usual. Sites
without modern deployment keep their current behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ErQwQQUZfaxvDvWaVGBoe4
@AbdullatifCengiz
AbdullatifCengiz merged commit 4676d80 into 4.x Oct 7, 2026
4 checks passed
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.

4 participants