Repository navigation
Add Maven Central publishing for SalesforceReact - #492
Merged
brandonpage merged 2 commits intoAug 27, 2026
Merged
Conversation
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||
wmathurin
approved these changes
Aug 27, 2026
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
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.
What
Adds the infrastructure to publish the
com.salesforce.mobilesdk:SalesforceReactAAR to Maven Central from this repo.When the Android bridge moved here from
SalesforceMobileSDK-Android/libs/SalesforceReact, the npm (react-native-force) publishing came along but the Maven Central publishing did not — there was no infrastructure to publish the artifact from this repo. This adds it, mirroring the Android repo's setup.Changes
settings.gradle.kts(exposesandroid/as:SalesforceReact),build.gradle.kts(nexus-publish plugin),gradle.properties, and the Gradle wrapper.buildSrc/publish-module.gradle.kts:maven-publish+signingconvention plugin (POM points at this repo).publish/:publish.shandpublish-root.gradle(Central Portal / signing credentials fromlocal.propertiesor env), matching the Android repo.android/build.gradle: applies the publishing config, guarded byrootProject.nameso it is a no-op during React Native autolinking in consumer apps.Version handling
Both the published Maven version and the
MobileSyncdependency version are read frompackage.json(the single source of truthsetversion.shstamps), so RC→GA bumps need no Gradle edits and the SalesforceReact artifact always depends on the matching MobileSync version.Notes
MobileSync(and its transitive SDK libs) to be released to Maven Central first, sinceandroid/build.gradlenow consumes it as a binary Maven dependency rather than a project dependency.local.properties(signing/Central credentials) stays gitignored.