Merged
Conversation
NonSwag
force-pushed
the
feat/proguard-mappings-publish
branch
from
b90fd80 to
d60d938
Compare
Member
|
I added the breaking API changes here: The new endpoint is documented in the README, so you can easily refactor to it |
NonSwag
force-pushed
the
feat/proguard-mappings-publish
branch
from
2379b0b to
47743d8
Compare
Member
Author
|
All required changes on my end are done. Also, don't forget to get #32 merged first. |
Member
Author
|
Also, this requires a docs update. Just so we don't forget. |
Member
We already got a PR open for the docs |
LuggaPugga
force-pushed
the
feat/proguard-mappings-publish
branch
from
93d8796 to
0bfe380
Compare
… GitHub Actions workflow
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
2 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.
No description provided.