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: README.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -353,11 +353,17 @@ package and push the .jar every time a commit changes a source file).
353
353
354
354
## Releasing
355
355
356
+
Releasing must be done by users authorized to push to the `org.jruby` group ID on https://central.sonatype.org and to push the `jruby-rack` gem to https://rubygems.org.
357
+
356
358
* Make sure auth is configured for "central" repository ID in your `.m2/settings.xml`
357
-
* Update the version in `src/main/ruby/jruby/rack/version.rb` to the release version
358
-
*`./mvnw release:prepare`
359
-
*`./mvnw release:perform` (possibly with `-DuseReleaseProfile=false` due to Javadoc doclint failures for now)
359
+
* Update the versions in `pom.xml` and `src/main/ruby/jruby/rack/version.rb` to the release version
360
+
* Commit the version update locally
361
+
* Run `./mvnw deploy -Prelease` to build, sign, and push all artifacts to Maven Central staging
362
+
* Once verified by Maven Central, authorize the deployment of the release on https://central.sonatype.org
360
363
*`rake clean gem SKIP_SPECS=true` and push the gem
364
+
* Tag the release version in git
365
+
* Update the versions again to the next dev version (`-SNAPSHOT` for the Maven artifact in `pom.xml` and `.SNAPSHOT` for the gem in `version.rb`)
0 commit comments