Allow code apps to configure the "new version available" update banner (silent auto-update / suppression)

[andrewtheart]

Type: Feature request / enhancement

---

Summary

When a new version of a code app is published (pac code push / power-apps push), users who load the app on an outdated cached build see the host-rendered banner:

"You're using an old version of this app. Refresh to use the latest version." — with a Refresh button.

This appears the first time a user opens the app after an update they haven't picked up yet. It does not show after they refresh or load the same link later (whether or not they click the Refresh button).

There is currently no supported way for a code app to control this behavior. We'd like an option to either force a silent auto-update (reload to latest with no prompt) or keep the current manual banner - ideally configurable per app.

Current behavior

• The banner is rendered by the Power Apps player/host shell (the parent frame at apps.powerapps.com), not by the code app itself. Because it's cross-origin, app code/CSS cannot interact with it.
• It is the same notification documented for canvas apps in Save and publish canvas apps → In-app notifications for new versions, which lists where it appears but provides no opt-out.
• The @microsoft/power-apps SDK exposes only setConfig({ logger }) and getContext() - no version/update API.
• power.config.json contains only deployment metadata (appId, environmentId, buildPath, data sources) - no update-behavior setting.

Net result: there is no maker, admin, environment, SDK, or config surface to suppress the banner or force a silent update.

Desired behavior

A supported, documented way to configure update behavior for a code app, for example one of:

1. Silent auto-update - when a new version is published, the app reloads to the latest build automatically (before app routing runs), without showing the banner.
2. Suppress banner - never show the update prompt (users pick up the new version on their next manual reload).
3. Manual (current behavior) - keep the existing banner + Refresh button.

A per-app setting (e.g. a field in power.config.json or an SDK config option) would let teams choose the mode and revert if needed.

Use case / motivation

Primary motivation - deep links with custom query parameters run against stale code.
We send users deep links to the app's play URL with custom query parameters that drive in-app routing and behavior. When a user opens one of these links on an outdated cached build, the app's routing code reads and acts on those parameters before the update banner is ever shown - so the stale version handles the request instead of the current code. A silent auto-update (or a forced refresh that completes before routing runs) would guarantee that the latest build processes these parameterized links.

Secondary motivations.

• We deploy code-app updates frequently and want users to always be on the latest build, especially after fixes that depend on backend/schema changes - without the jarring experience of having to see the banner and click Refresh.

Proposed shape (illustrative)

// power.config.json
{
  "appId": "...",
  "environmentId": "...",
  "updateBehavior": "silent" // "silent" | "suppress" | "manual" (default: "manual")
}

…or an SDK option:

import { setConfig } from "@microsoft/power-apps/app";
setConfig({ updateBehavior: "silent" });

Environment

• Code app (React + Vite + TypeScript), @microsoft/power-apps client library.
• Run via standalone play URL: https://apps.powerapps.com/play/e/{environmentId}/app/{appId}.