Skip to content
New issue

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

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

Already on GitHub? # to your account

[release/8.0.1xx] Bump version to generate 8.0.1.x versioning #18491

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

dalexsoto
Copy link
Member

No description provided.

@dalexsoto dalexsoto requested a review from a team as a code owner November 2, 2023 18:40
@dalexsoto dalexsoto requested review from StephaneDelcroix and rachelkang and removed request for a team November 2, 2023 18:40
@Redth Redth enabled auto-merge (squash) November 2, 2023 18:46
Copy link
Member

@pjcollins pjcollins left a comment

Choose a reason for hiding this comment

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

Looking at the build outputs (including vs-workload.props), the NuGets are versioned 8.0.2 and we now have a VS component version of Version="8.0.2.0". I'm assuming some commit distance info is being added to this base versioning? If so we may only need one empty commit on top of this branch if we want to get an 8.0.1 version, but 8.0.2 should be fine either way.

@jonathanpeppers
Copy link
Member

Maybe the extra distance is just how AzDO works? It merged the target branch on top of this one? Maybe when merged it would come out 8.0.1.

@mattleibow
Copy link
Member

Yeah, the title is a bit misleading, the final nugets will be 8.0.1 and then 8.0.2.

@Redth Redth merged commit 073a8c4 into release/8.0.1xx Nov 2, 2023
@Redth Redth deleted the net8versionbump branch November 2, 2023 20:29
@github-actions github-actions bot locked and limited conversation to collaborators Dec 5, 2023
@samhouts samhouts added the fixed-in-8.0.3 Look for this fix in 8.0.3 label Aug 2, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
fixed-in-8.0.3 Look for this fix in 8.0.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants