[Feature] Extend ExtensionInstance.deployConfig to include app config info

[EliasJRH]

WHY are these changes introduced?

Part of https://github.com/Shopify/flow/issues/21604, allows app extensions, such as Flow actions, to access application configuration data such as the application url.

WHAT is this pull request doing?

This PR extends the ExtensionInstance.deployConfig method such that it requires an appConfiguration which is obtained from the callsite in extension-instance.ts. Extensions can now implement deployConfig in their createExtensionSpecification functions and use the fields in the passed appConfiguration

How to test your changes?

Post-release steps

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

[Copilot]

Pull request overview

This PR extends the extension deployment configuration hook so extension specifications can access the app’s configuration (e.g., app URLs) when building their deployConfig payload.

Changes:

• Extends ExtensionSpecification.deployConfig signature to accept an optional context containing appConfiguration.
• Updates ExtensionInstance.deployConfig to pass appConfiguration into the specification’s deployConfig call.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/app/src/cli/models/extensions/specification.ts	Extends the deployConfig function type to accept a context that can carry appConfiguration.
packages/app/src/cli/models/extensions/extension-instance.ts	Passes appConfiguration from the callsite into specification.deployConfig via the new context argument.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.