-
Notifications
You must be signed in to change notification settings - Fork 23
Maintenance instructions
Andrew Guibert edited this page Nov 11, 2019
·
5 revisions
In this example, suppose the latest release is 0.4.1
and the project is currently at version 0.4.2-SNAPSHOT
. We will be performing a release of version 0.4.2
and then updating the project to version 0.4.3-SNAPSHOT
.
- Run the task:
./gradlew updateVersion -PnextVersion=0.4.2
- Run the task:
./gradlew publish
to publish release artifacts to maven central staging - Log in to your Sonatype account at https://oss.sonatype.org/
- Go to the
Staging Repositories
tab and refresh. You will see a staging repo ID such asorgmicroshed-1011
- To test the new release in staging, add the following repository config:
<repositories> <repository> <id>sonatype-staging</id> <url>https://oss.sonatype.org/service/local/repositories/${STAGING_REPO_ID}/content/</url> </repository> </repositories>
- If the new release test out OK, press the
Close
button to close the staging repository. - Press the
Release
button to release the artifacts to Maven Central. - Draft a new release on Github: https://github.com/MicroShed/microshed-testing/releases
- Update to the next development snapshot version:
./gradlew updateVersion -PnextVersion=0.4.3-SNAPSHOT
and make a PR with these changes
Dependency updates to source modules should happen automatically via Dependabot PRs. If you want to perform additional checking, you can run the ./gradlew dependencyUpdates -Drevision=release
task.