Change StabilizePackageVersion to false condition

[Jose Perez Rodriguez (joperezr)]

No description provided.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20403

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20403"

[github-actions]

Tests selector

Selects the full PR test matrix + all PR-gated jobs (ALL) — a rule matching 'eng/Versions.props' selects ALL

---

Selection computed for commit 532b6a3.

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused configuration change has no unresolved issues.

Review effort: Balanced
Findings: None

What changed in this PR

Makes package version stabilization opt-in, preserving prerelease versions for normal builds.

Changes:

• Defaults StabilizePackageVersion to false.
• Preserves explicit stabilization overrides.

File	Description
eng/​Versions.props	Changes package stabilization to opt-in.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[aspire-repo-bot]

✅ No documentation update needed.

Step 5 branch taken: docs_optional → build_or_ci_only

Triggered signals: no signals triggered (signal_count: 0, recommendation: "docs_optional").

Allowlist justification: The only changed file is eng/Versions.props (1 addition, 1 deletion), which is a top-level build/engineering configuration file. This matches the build_or_ci_only category (only files under eng/, .github/, playground/, or top-level build config changed). The only_test_or_build_changes advisory signal is also true, corroborating this.

Change nature: The PR title ("Change StabilizePackageVersion to false condition") and the single-file diff indicate this is an internal build-property condition tweak controlling package version stabilization behavior during the build/release process. It has no public API surface, CLI, dashboard, or user-facing configuration impact — it only affects internal engineering/release tooling. No docs PR is warranted.