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
Releases of Grails are automated by [Travis CI](https://travis-ci.org/grails/grails-core).
32
+
33
+
To create a release perform the following steps first update the Grails version in `build.gradle` and `grails-core/src/test/groovy/grails/util/GrailsUtilTests.java` then add them to git:
After pushing these changes to the repository and wait for the build to complete. During this phase the JAR files will be uploaded to the [Grails Artefactory Repository](https://repo.grails.org/grails/libs-releases-local/).
40
+
41
+
Once the build completes successfully then tag the release using Git. The tag should begin with the letter 'v'. For example:
42
+
43
+
$ git tag v3.0.1
44
+
$ git push --tags
45
+
46
+
The tagged release will be automatically uploaded to [Sonatype OSS](https://oss.sonatype.org) and [Github Releases](https://github.com/grails/grails-core/releases).
47
+
48
+
Although Grails doesn't require the JARs to be in Maven Central for a release, without signing in releasing the staged release via Sonatype OSS the JARs will not be synced to Maven Central.
0 commit comments