Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

experimental insertion should not push non-preview packages #11492

Open
JanProvaznik opened this issue Feb 25, 2025 · 0 comments · May be fixed by #11534
Open

experimental insertion should not push non-preview packages #11492

JanProvaznik opened this issue Feb 25, 2025 · 0 comments · May be fixed by #11534
Assignees
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Priority:1 Work that is critical for the release, but we could probably ship without triaged

Comments

@JanProvaznik
Copy link
Member

JanProvaznik commented Feb 25, 2025

when experimentally inserting in servicing branches the package version does not have a preview suffix, this then leads to package conflicts when we want to upload the real packages on merge.

It likely should be fixed in MSBuild CI pipeline.

rainersigwald pushed a commit that referenced this issue Feb 25, 2025
.15 packages were pushed because of #11492.
@maridematte maridematte added Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Priority:1 Work that is critical for the release, but we could probably ship without triaged labels Feb 26, 2025
rainersigwald added a commit that referenced this issue Feb 27, 2025
(again, hit #11492).
@JanProvaznik JanProvaznik self-assigned this Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Our Own Build Problems affecting the build or build infrastructure of the MSBuild repo itself. Priority:1 Work that is critical for the release, but we could probably ship without triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants