Publish prebuilt releases to npm, SDKMAN, Homebrew, and WinGet.
brew install aalsanie/tap/distroplaneOn Windows:
winget install --id Aalsanie.Distroplane --exactBuild your artifact first, then run:
distroplane init
distroplane doctor
distroplane publishFollow the prompts to choose a destination, provide its required metadata and approve the release. Credentials stay in environment variables, not configuration files.
To check or continue an existing release:
distroplane status
distroplane resumeDo not delete .distroplane/ while a release may still need recovery.
Add the published Maven plugin to <build><plugins> in your pom.xml:
<plugin>
<groupId>io.github.aalsanie</groupId>
<artifactId>distroplane-maven-plugin</artifactId>
<version>1.0.0</version>
<configuration>
<cliVersion>0.9.2</cliVersion>
<config>distroplane.json</config>
</configuration>
</plugin>With a prebuilt artifact and distroplane.json, run mvn io.github.aalsanie:distroplane-maven-plugin:1.0.0:plan to review a release. Maven usage.
Publish a prebuilt artifact from a GitHub Actions workflow:
- uses: aalsanie/distroplane@main
env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
with:
version: 0.9.3
command: publish
approve: 'true'
credential-mappings: npm-publish=NPM_TOKENRequires distroplane.json in the checked-out repository and a configured npm destination. Pin the Action to a reviewed commit in production. GitHub Action usage.
CLI · Configuration · Security · Changelog
Apache-2.0.