Skip to content

update version prefix to 18.3#12786

Merged
SimaTian merged 3 commits intomainfrom
update-branding-18.3
Nov 19, 2025
Merged

update version prefix to 18.3#12786
SimaTian merged 3 commits intomainfrom
update-branding-18.3

Conversation

@SimaTian
Copy link
Member

part of #12522

Copilot AI review requested due to automatic review settings November 18, 2025 20:57
@SimaTian SimaTian requested a review from a team as a code owner November 18, 2025 20:57
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the MSBuild version prefix from 18.1.0 to 18.3.0, advancing the project's version number as part of the versioning strategy outlined in issue #12522.

  • Updated version prefix from 18.1.0 to 18.3.0

@SimaTian SimaTian merged commit d11f401 into main Nov 19, 2025
10 checks passed
@SimaTian SimaTian deleted the update-branding-18.3 branch November 19, 2025 10:01
ViktorHofer added a commit that referenced this pull request Jan 12, 2026
Work item (Internal use): 

### Summary

Updates MSBuild version branding from 18.3 to 18.4 following the pattern
established in #12786.

**Changes:**
- `eng/Versions.props`: Bump `VersionPrefix` from `18.3.0` to `18.4.0`
- `azure-pipelines/vs-insertion.yml`: Add `rel/d18.4` target branch and
`vs18.4` branch mapping
- `.config/git-merge-flow-config.jsonc`: Configure merge flow chain as
vs18.0 → vs18.3 → vs18.4 → main

**Note:** Creating the `vs18.3` servicing branch requires write
permissions and must be done separately.

### Customer Impact

None. Branding update only affects internal version strings and CI/CD
pipeline configuration for VS insertions and branch merge flows.

### Regression?

No. Configuration-only changes to version strings, build pipeline
mappings, and merge flow automation.

### Testing

- Repository build successful
- MSBuild version reports `18.4.0-dev`
- Sample project builds without errors
- JSONC syntax validation passed
- Code review and security scans passed

### Risk

Low. Minimal surface area—version string, pipeline configuration, and
merge flow updates following established pattern from previous version
bumps.

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Snap for vs18.3 and update branding to
vs18.4</issue_title>
> <issue_description>- [ ] Mimic what was done in
#12786 but for vs18.4 instead of
vs18.3
> - [ ] Create a vs18.3 branch with
https://github.com/dotnet/msbuild/tree/fb775842a00d534aaf25466ff76e0d8fe86d2e7d
as the HEAD SHA</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #13004

<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in
our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: ViktorHofer <7412651+ViktorHofer@users.noreply.github.com>
Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.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.

3 participants