Push to main. Hye ships it.
Connect your repo and we build, sign, and publish every release. Or keep your own pipeline and call us when the artifact is ready. Either way, your buyers get the new version within a minute.
Pick whichever fits your stack.
Use hye CI
Connect your GitHub or GitLab repo. We detect Gradle, Maven, or Bukkit/Forge/Fabric configs and build the artifact on every tag (or on every push to a branch you pick). Signed provenance shipped with every release.
- Multi-version test matrix (1.20, 1.21, 1.21.1, …)
- Auto-bump version from git tag
- Artifact signed by hye build attestation key
- Auto-published as a draft for your review
- Free for any hye creator account
Bring your own pipeline
Already on GitHub Actions, Jenkins, GitLab CI, or anything else? Authenticate with a scoped API token and POST your artifact + changelog. Hye does the rest.
- GitHub Actions (drop-in workflow snippet)
- Jenkins / GitLab CI / CircleCI (REST endpoint)
- Custom — anything that can POST a file
- Token scopes per project, per environment
- Free for any hye creator account
What we do for you.
Project detection
We detect your loader and build tool from gradle/build.gradle/pom.xml/fabric.mod.json.
Build cache
Per-creator Gradle / Maven cache so back-to-back builds run in seconds.
Test matrix
Run your test suite across each MC version your plugin claims to support. PR fails are surfaced before publish.
Concurrent builds
Up to 5 parallel jobs per creator. Soft fair-share when usage spikes.
Build logs
Full job log retained for 30 days. Searchable. Sharable read-only links.
Cancel mid-flight
Click cancel and the worker stops within 5 seconds. No half-billed minutes (because we don't bill).
For people who already have CI they trust.
GitHub Actions
uses: hye-marketplace/publish-action@v1. Drop-in workflow.
Jenkins
Add a post-build step calling our REST endpoint with your token + artifact path.
GitLab CI
hye-publish Docker image, set HYE_TOKEN, run on tag pipelines.
Anything else
Authenticated POST to https://api.hye.gg/v1/dashboard/projects/:id/versions/upload. We accept JAR + manifest.
Example: GitHub Actions
- name: Publish to Hye
uses: hye-marketplace/publish-action@v1
with:
token: ${{ secrets.HYE_TOKEN }}
project-id: 'paper-economy-plus'
artifact: build/libs/*-all.jar
changelog: CHANGELOG.mdSigned and audited.
Whichever pipeline you use, the artifact lands on hye with the same provenance footprint.
Sigstore-style attestation
Each artifact is signed; the attestation includes the source commit, the workflow file hash, the runner identity, and the timestamp.
Audit log entry
Publish events appear in your project's audit log. Buyers see a public 'Verified build from <repo>@<commit>' badge on the version.
Reproducible by design
Anyone with the source can re-run the build and verify the artifact matches. Hye stores the build inputs so a maintainer can reproduce a 6-month-old release.
Tokens are scoped on purpose.
Don't paste full account credentials into your CI.
Per-project scope
A token can publish to ONE project, not your whole catalog.
Per-environment scope
Mark a token as draft-only or live. A staging token can never push a production version.
Rotate without downtime
Issue the new token, deploy it, revoke the old one. We give you a 24h overlap window.
Audit per token
Each publish action records which token was used. Lose your laptop → revoke that token, see exactly what it shipped.
Free for everyone.
Hye CI minutes are free for any creator account. We charge zero per-build, zero per-minute, zero per-artifact. The only thing we sell is the marketplace position once your project ships — and you set the price for that.
Ready to wire it up?
Connect a repo or generate a token.