Skip to content

Update releasing.md with BAR ID instructions - #55659

Open
nagilson wants to merge 2 commits into
release/dnupfrom
nagilson-clarify-promo-instruction
Open

Update releasing.md with BAR ID instructions#55659
nagilson wants to merge 2 commits into
release/dnupfrom
nagilson-clarify-promo-instruction

Conversation

@nagilson

@nagilson nagilson commented Aug 6, 2026

Copy link
Copy Markdown
Member

Clarify instructions for finding BAR ID and promoting builds.

Clarify instructions for finding BAR ID and promoting builds.
Copilot AI review requested due to automatic review settings August 6, 2026 23:25
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Clarifies the dotnetup release documentation by adding guidance on where to find the BAR ID when it’s not present in build tags, and by refining the parameter guidance for build promotion.

Changes:

  • Add a note explaining how to locate the BAR ID in the pipeline logs when it’s missing from build tags.
  • Clarify which build-promotion parameter should receive /p:BuildQuality=preview.

Comment thread documentation/general/dotnetup/releasing.md Outdated
| `BARBuildId` | The BAR ID from the selected build |
| `PromoteToChannelIds` | `10506` (`dotnetup Daily`) |
| `ArtifactsPublishingAdditionalParameters` | `/p:BuildQuality=preview` |
| `ArtifactsPublishingAdditionalParameters` ( NOT `symbol` parameters ) | `/p:BuildQuality=preview` |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants