You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/internal/releasing.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ When ready, merge the pull request.
48
48
### Credentials
49
49
50
50
The library is published to Maven Central by the `firebase-sonatype` account, Googlers can find the
51
-
password for this account in [Valentine](http://go/valentine/)
51
+
password for this account in [Valentine](http://go/valentine/).
52
52
53
53
### GPG Key
54
54
@@ -100,8 +100,8 @@ sudo pkill dirmngr
100
100
101
101
### Local Properties
102
102
103
-
1. Navigate to https://oss.sonatype.org/ and **Log In** using the credentials from [Valentine](http://go/valentine).
104
-
1.Follow [these instructions](https://central.sonatype.org/publish/generate-token/) to **Access User Token**.
103
+
1. Navigate to https://central.sonatype.com/ and **Log In** using the credentials from [Valentine](http://go/valentine).
104
+
1.Go to [View user tokens](https://central.sonatype.com/usertoken) and generate a new token.
105
105
You should see an XML that looks like this:
106
106
```xml
107
107
<server>
@@ -122,11 +122,6 @@ mavenCentralPassword=<PASSWORD FROM THE XML ABOVE (eg. tokenkey-dlghnfgh8+4LfXmg
122
122
123
123
## 2b - Publish and release
124
124
125
-
_Publish_ and _release_ [used to be done](https://github.com/firebase/FirebaseUI-Android/blob/9.0.0/docs/internal/releasing.md#2b---publish-and-release)
126
-
in two separate manual steps, but starting in [v0.22.0](https://vanniktech.github.io/gradle-maven-publish-plugin/changelog/#0220-2022-09-09)
127
-
of the `com.vanniktech:gradle-maven-publish-plugin`, the `publishAllPublicationsToMavenRepository`
128
-
now handles the _publish_ step automatically and you only need to perform the _release_ manually.
129
-
130
125
Once you are sure the release branch is healthy, run the following commands:
131
126
132
127
```shell
@@ -136,9 +131,10 @@ Once you are sure the release branch is healthy, run the following commands:
0 commit comments