Change StabilizePackageVersion condition to true

[Jose Perez Rodriguez (joperezr)]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No

[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 -- 20368

Or

• Run remotely in PowerShell:

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

[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 fab804b.

[Copilot]

Copilot review overview

🟡 Changes recommended

The new global default breaks normal CI channel selection and local prerelease hive packaging.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Stabilization default changes ordinary builds to stable release artifacts · New

What changed in this PR

Changes the default package versioning mode from prerelease to stabilized release builds.

Changes:

• Sets StabilizePackageVersion to true by default.
• Consequently selects release versioning and the stable CLI channel.

File	Review
eng/​Versions.props	Critical: Normal CI builds may produce stable artifacts and use the stable CLI channel. Moderate: Local hive scripts may fail to copy prerelease packages due to filename mismatches.

---

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

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[Jose Perez Rodriguez (joperezr)]

The failure is unrelated, seems to be #20117

[aspire-repo-bot]

✅ No documentation update needed.

Step 5 branch taken: docs_optional → build_or_ci_only

Triggered signals: none triggered (signal_count == 0; only_test_or_build_changes is advisory-only and not a gating signal).

Allowlist justification: All 1 changed file (eng/Versions.props) matches the eng/ build-configuration glob. The change is a single-line edit (StabilizePackageVersion condition flipped to true) in a build/versioning props file consumed by the build pipeline, not by any documented public API, CLI surface, or user-facing behavior. This cleanly matches the build_or_ci_only allowlist category defined in Step 5.