gradle-semantic-release-plugin
Advanced tools
Yet another gradle-semantic-release-plugin that invokes Gradle wrapper script to release.
To apply this semantic-release plugin, you need to fulfill the following preconditions:
gradle.properties (not by build.gradle nor build.gradle.kts)../gradlew.Follow install guide and CI configuration guide described in the semantic-release official document.
To manage version of toolset, we recommend you to have a package.json in your project root directory. Manage both of semantic-release and its plugins as devDependencies.
It is also nice to have "semantic-release": "semantic-release" in "scripts" in package.json, then you can run yarn semantic-release to invoke semantic-release.
Refer this sample project as a working example.
@semantic-release/gitThis plugin updates gradle.properties to bump up project version. If you want to keep the version in this file updated, configure @semantic-release/git to commit changes. You can configure your package.json like below:
"release": {
"plugins": [
"gradle-semantic-release-plugin",
[
"@semantic-release/git",
{
"assets": [
"gradle.properties"
]
}
]
]
},
If your CI configuration is for java app development, then you may need to install node by your own.
For Travis CI, it has nvm in the PATH so you can install them like below:
language: java
before_install: # or at the release stage described in the following part
- nvm install 12
- npm ci # or "yarn
Then trigger semantic-release at the release stage. For now the build stage is recommended over the travis-deploy-once:
jobs:
include:
- stage: release
script: skip
deploy:
provider: script
skip_cleanup: true
script:
- npm run semantic-release # or "yarn semantic-release"
That is a Gradle plugin implemented by Java. It can use Gradle's feature and ecosystem. However, it emulates semantic-release and cannot use other semantic-release plugin at the same time.
Our plugin is a semantic-release plugin. It can work with other plugin implemented on node.js, but it just invokes Gradle and cannot handle so complex requirements by own.
Copyright (c) 2019 Kengo TODA
FAQs
Automated release management for Gradle project
The npm package gradle-semantic-release-plugin receives a total of 5,074 weekly downloads. As such, gradle-semantic-release-plugin popularity was classified as popular.
We found that gradle-semantic-release-plugin demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.