@mythicdrops/semantic-release-gradle-config
Advanced tools
semantic-release preset for MythicDrops Gradle projects.
semantic-release shareable config to publish MythicDrops Gradle projects to Maven Central.
This shareable configuration use the following plugins:
@semantic-release/changelog@semantic-release/commit-analyzer@semantic-release/git@semantic-release/github@semantic-release/release-notes-generator@mythicdrops/semantic-release-sonatype$ npm install --save-dev semantic-release @mythicdrops/semantic-release-gradle-config
The shareable config can be configured in the semantic-release configuration file:
{
"extends": "@mythicdrops/semantic-release-gradle-config"
}
See each plugin documentation for required installation and configuration steps.
Supported release branches can now happen as below:
mainN.N.x or
N.x.x or N.x with N being a number)next distribution channel from the branch next if it existsnext-major distribution channel from the branch
next-major if it existsbeta distribution channel from the branch beta if it existsalpha distribution channel from the branch alpha if it existsFAQs
semantic-release preset for MythicDrops Gradle projects.
We found that @mythicdrops/semantic-release-gradle-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
Research
/Security News
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.