[spetersenms]

❔What, Why & How

From BC30 and later we will use the new Admin API to handle PTE publishing and installing. This is due to the old API getting deprecated.

All new deployment logic is handled 100% by AL-Go and does not rely on BcContainerHelper. Cleanup of old versions are now automated by the environment with no options for a manual API call, which means the unpublishOldVersions setting is deprecated already and only relevant for BC29 and below.

Deployments using the new API require additional Admin Center permissions, which is documented.

Related to issue: #

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry

[Copilot]

🟡 Changes recommended

The documentation omits that Scope Dev deployments installing or upgrading PTE dependencies on BC 30+ still require additional Admin Center API authorization and can fail without it.

1 open issue

• Narrow Scope Dev exemption for PTE dependency deployments · New

What changed in this PR

This PR moves AL-Go’s PTE publishing and installation to the Admin Center API for Business Central 30 and later, while preserving legacy publishing for earlier versions.

Changes:

• Adds a shared, version-aware publisher with multipart uploads, operation polling, and bounded retries for transient status failures.
• Routes primary apps and PTE dependencies through the shared publisher and skips explicit old-version cleanup on BC 30+.
• Adds deployment tests and documents authorization requirements and service-managed cleanup.

File	Description
Workshop/​ContinuousDeployment.md	Documents authorization and cleanup behavior.
Tests/​UnpublishOldAppVersions.Test.ps1	Tests cleanup version boundaries and unknown versions.
Tests/​PublishPTEApps.Test.ps1	Tests routing, uploads, polling, and failure handling.
Tests/​Deploy.Module.Test.ps1	Tests shared publishing for PTE dependencies.
Tests/​Deploy.Action.Test.ps1	Tests action integration and cleanup sequencing.
Scenarios/​settings.md	Updates deployment authorization and cleanup guidance.
Scenarios/​RegisterSandboxEnvironment.md	Adds sandbox authorization instructions.
Scenarios/​RegisterProductionEnvironment.md	Adds production authorization instructions.
RELEASENOTES.md	Announces authorization and cleanup changes.
Actions/​Deploy/​README.md	Describes publishing behavior and permissions.
Actions/​Deploy/​Deploy.psm1	Implements shared publishing and version-aware cleanup.
Actions/​Deploy/​Deploy.ps1	Uses the shared publisher for primary PTE apps.
Actions/​.Modules/​settings.schema.json	Aligns the cleanup setting description with version-specific behavior.

_{Review effort: Balanced}