fix(core): Persist scalar custom fields in updateGlobalSettings with relations

[biggamesmallworld]

Summary

• Fixes updateGlobalSettings mutation not persisting scalar custom field values when a relational custom field is also defined on GlobalSettings
• Saves the entity to DB before calling updateRelations(), matching the pattern used by other services (e.g. CollectionService, FacetService)
• Adds e2e test verifying scalar + relational custom fields persist together

Fixes #4342

Test plan

• Existing custom-field-relations e2e tests pass (59/59)
• Existing global-settings e2e tests pass (7/7)
• New test verifies scalar values persist when updated alongside relations
• New test re-queries after mutation to confirm DB persistence

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
vendure-storybook	Ready	Preview, Comment	Feb 17, 2026 1:10pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/global-settings-custom-field-relations

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}