chore: register new NuGet package versions#6
Closed
spbsoluble wants to merge 1 commit into
Closed
Conversation
spbsoluble
force-pushed
the
chore/upgrade-nuget-packages
branch
from
d99ce62 to
c71ad06
Compare
spbsoluble
force-pushed
the
chore/upgrade-nuget-packages
branch
from
c71ad06 to
1d30876
Compare
Collaborator
Author
|
Closing — this PR contained a duplicate version entry caused by a prefix-matching bug in the upgrade script (fixed in bdec440). A corrected PR has been generated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by the weekly upgrade workflow.
New versions registered
After merging, the daily Sync NuGet Packages workflow will push the new versions to the GitHub Package Registry, or you can trigger it manually.