Skip to content

Keep target collection ids when deploying to a different project - #1607

Open
midigofrank wants to merge 1 commit into
mainfrom
fix-1606
Open

midigofrank wants to merge 1 commit into
mainfrom
fix-1606

Conversation

@midigofrank

Copy link
Copy Markdown
Contributor

Short Description

Sandbox merges took the local collections as-is, so every cross-project deploy sent freshly minted ids for collections the target already had, and Lightning rejected the update with a 500. Match them to the target's collections by name, as same-project deploys already do.

Fixes #1606

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

Sandbox merges took the local collections as-is, so every cross-project
deploy sent freshly minted ids for collections the target already had,
and Lightning rejected the update with a 500. Match them to the target's
collections by name, as same-project deploys already do.

Fixes #1606
@midigofrank midigofrank self-assigned this Oct 30, 2026
@github-project-automation github-project-automation Bot moved this to New Issues in Core Oct 30, 2026
@midigofrank
midigofrank marked this pull request as ready for review October 30, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

Cross-project deploy fails with 500 once the target project has collections

1 participant