[release/9.0] Fix SignalR Java POM to include description #58896
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
requested review from
BrennanConroy and
halter73
as code owners
dotnet-issue-labeler
bot
added
the
area-signalr
BrennanConroy
added
ask-mode
dotnet-policy-service
bot
added
the
pending-ci-rerun
|
@BrennanConroy does this need fixing up? |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
wtgodbe
approved these changes
Nov 27, 2024
This was referenced Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #58895 to release/9.0
/cc @BrennanConroy
Fix SignalR Java POM to include description
Description
When updating our macOS CI machines, due to the ones we were using about to be removed, we had to update our gradle reference (what builds java). This update contained many breaking changes which required a lot of work to update how we bundle our packages. Unfortunately, we missed some metadata during the update which prevents the packages from being published.
Customer Impact
Version 9.0 of our Java packages are not published.
Regression?
Risk
Changing metadata not code, locally validated that the file contains the missing metadata.
Verification
Packaging changes reviewed?