When you release fixed version of SpotBugs, please follow these procedures.
version
inbuild.gradle
- version number in
CHANGELOG.md
version
,full_version
,maven_plugin_version
andgradle_plugin_version
indocs/conf.py
The PR containing these changes needs to be rebased and merged to master. Since the rebase changes the commit ids, a tag needs to be created on master and pushed there. The push of this tag starts the release CI job.
When we push a tag, the build result on GitHub Actions will be deployed to the SonaType Nexus, and published to the Maven Central automatically by Gradle Nexus Publish Plugin. Then we can find artifacts in the Maven Central after several hours.
See the build
phase in .github/workflows/release.yml
calling the publishToSonatype
and closeSonatypeStagingRepository
gradle tasks.
It's automated by GitHub CI.
When we push tag, the build result will be deployed to eclipse-candidate repository.
When we push tag and its name doesn't contain _RC
, the build result will be deployed to eclipse repository.
See Deploy eclipse
, Deploy eclipse-candidate
and Deploy eclipse-latest
phases in .github/workflows/release.yml
for detail.
Update version in Eclipse Marketplace page. If you have no permission, please contact with @KengoTODA or @iloveeclipse.
This project is not released directly to the Gradle Plugin Portal, that is the role of the SpotBugs Gradle Plugin project.
See docs/README.md for detail.
The CHANGELOG
on the GitHub release page only contains a link to the correct version of the CHANGELOG.md
file (see createReleaseBody
task in build.gradle
). It needs to be manually updated after the new GitHub release is created.