Update ojg to latest release #2357
Merged
Conversation
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
tuunit
requested changes
Dec 28, 2023
Member
tuunit
left a comment
There was a problem hiding this comment.
Hi @bitfehler,
please add an entry for this PR to the CHANGELOG.md
The previously used release is no longer available on Github.
Contributor
Author
|
Done |
3 tasks
JoelSpeed
approved these changes
Jan 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The previously used release is no longer available on Github.
Description
When building the current master branch, I get the following error:
And indeed, the latest tag to be found over at ojg is 1.15.0. This is obviously a tad strange, not sure how a tag would disappear, but I leave that judgement up to you. After this patch, oauth2-proxy builds fine for me.
Motivation and Context
How Has This Been Tested?
Checklist: