Add doNotPerformUpgrade setting and enhance upgrade warning messages

[ChrisBlankDe]

❔What, Why & How

This pull request introduces a new pipeline setting, doNotPerformUpgrade, which allows users to skip the upgrade phase in Run-AlPipeline while continuing to publish and test apps. The setting is integrated into the configuration schema, documented for users, and tested for presence in the schema. Additionally, warning messages related to upgrade testing have been improved for clarity.

New Feature: Skip Upgrade Phase

• Added a new doNotPerformUpgrade boolean setting to the default settings in ReadSettings.psm1, the pipeline schema (settings.schema.json), and pipeline parameter list in RunPipeline.ps1, allowing users to bypass the upgrade phase during pipeline execution.
• Documented the new setting in RELEASENOTES.md and Scenarios/settings.md, explaining its purpose and usage.
• Added a test to ensure doNotPerformUpgrade is present in the settings schema.

Pipeline Usability Improvements

• Enhanced warning messages in RunPipeline.ps1 to clarify that missing previous release apps disables the AppSourceCop breaking change check.

Original PR #2297 was reverted with PR #2305. This PR matches the original, with the additional initialization of the settings.

Related to issue: #2296

✅ Checklist

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

[Copilot]

Pull request overview

Adds doNotPerformUpgrade to skip upgrade execution while retaining publishing and testing behavior.

Changes:

• Adds and forwards the new pipeline setting.
• Updates upgrade-related warnings and documentation.
• Adds schema validation coverage.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
Actions/.Modules/ReadSettings.psm1	Initializes the setting to false.
Actions/.Modules/settings.schema.json	Defines the boolean setting.
Actions/RunPipeline/RunPipeline.ps1	Forwards the setting and clarifies warnings.
Tests/ReadSettings.Test.ps1	Verifies schema presence and type.
Scenarios/settings.md	Documents the setting.
RELEASENOTES.md	Announces the feature.

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

Tests/ReadSettings.Test.ps1:547

• Close the new It block before the existing validation test. As written, the second It is nested and the file ends with an unmatched {, so this Pester file cannot be parsed or run.

            It 'ValidateSettings skips validation entirely on PS versions less than 7 without warning' {

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

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