Configure CircleCI to publish artifacts to Maven Central#34983
Closed
cortinico wants to merge 1 commit into
Closed
Configure CircleCI to publish artifacts to Maven Central#34983cortinico wants to merge 1 commit into
cortinico wants to merge 1 commit into
Conversation
facebook-github-bot
added
CLA Signed
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D40377691 |
Base commit: 0fcce54 |
Base commit: 0fcce54 |
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D40377691 |
cortinico
force-pushed
the
export-D40377691
branch
from
2bb7527 to
cd9e0fd
Compare
) Summary: Pull Request resolved: facebook#34983 This sets up our CircleCI logic to publish artifacts to Maven Central. I will check if tomorrow's nightly successfully landed on Maven Central Snapshot repository. I've added a --dry-run to the the close and release step of the publishing to avoid accidentally publishing to Maven Central. We'll remove this if we decide to go with the Maven Central publishing. Changelog: [Internal] [Changed] - Configure CircleCI to publish artifacts to Maven Central Differential Revision: D40377691 fbshipit-source-id: 0dacfc44f02ef5e973675fc4bba079fe4f3fa596
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D40377691 |
cortinico
force-pushed
the
export-D40377691
branch
from
cd9e0fd to
e6618bf
Compare
Collaborator
|
This pull request was successfully merged by @cortinico in 5d8a712. When will my fix make it into a release? | Upcoming Releases |
mohitcharkha
pushed a commit
to mohitcharkha/react-native
that referenced
this pull request
Oct 17, 2022
) Summary: Pull Request resolved: facebook#34983 This sets up our CircleCI logic to publish artifacts to Maven Central. I will check if tomorrow's nightly successfully landed on Maven Central Snapshot repository. I've added a --dry-run to the the close and release step of the publishing to avoid accidentally publishing to Maven Central. We'll remove this if we decide to go with the Maven Central publishing. Changelog: [Internal] [Changed] - Configure CircleCI to publish artifacts to Maven Central Reviewed By: jacdebug, huntie Differential Revision: D40377691 fbshipit-source-id: 36a74074ea95097bb7268352e40f4d2670f3cd65
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
4 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.
Summary:
This sets up our CircleCI logic to publish artifacts to Maven Central.
I will check if tomorrow's nightly successfully landed on Maven Central
Snapshot repository.
I've added a --dry-run to the the close and release step of the publishing
to avoid accidentally publishing to Maven Central. We'll remove this if
we decide to go with the Maven Central publishing.
Changelog:
[Internal] [Changed] - Configure CircleCI to publish artifacts to Maven Central
Differential Revision: D40377691