fix: open, close and promote from staging to maven #112
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
davisusanibar
force-pushed
the
feature/fix_promote_to_maven_central
branch
from
900cf3c to
eceb61d
Compare
|
Can you tell why this is failing checks? It seems like the failure is likely unrelated. Previous merge conflict? |
Just downgrade Gradle version as the same that initially was configured and all of it is working as expected. |
|
@jacques-n please your support on this PR. |
ajegou
pushed a commit
to ajegou/substrait-java
that referenced
this pull request
Mar 29, 2024
* fix: open, close and promote from Staging to Maven * fix: downgrade gradle wrapper version
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
To implement automatic promote from Staging to Maven Central on weekly releases.
Base on discussion on PR #104 (scenario 1 & 2).