Required Variables
The Hangar API key used to authenticate with the Hangar API.You can generate an API key from your Hangar settings under the “API Keys” section.Example:or with system properties:
The Hangar project slug where the version will be uploaded.You can find your project slug in your project’s URL (e.g., or with system properties:
EssentialsX from https://hangar.papermc.io/EssentialsX/EssentialsX).Example:The release channel for this version on Hangar.Channels allow you to organize versions by stability level. Common channels include: or with system properties:
Release, Beta, Alpha, Snapshot.Example:Space-separated list of Minecraft versions that this version supports.If not set, MCReleaser will use the common or with system properties:
GAME_VERSIONS variable as a fallback.Example:Optional Variables
The platform(s) that this version supports.Valid values: or with system properties:
PAPER, WATERFALL, VELOCITYYou can specify multiple platforms separated by spaces.Example:The dependencies of the artifact. This should be formatted according to Hangar’s API requirements.Dependencies define relationships between your plugin and other plugins on Hangar.Example:
Source Reference
Hangar properties are defined in:Complete Example
Using Environment Variables
Using System Properties
GitHub Actions Workflow
Tips
- Store your
HANGAR_KEYas a secret in your CI/CD system - Use the
Releasechannel for stable, production-ready versions - Use
BetaorAlphachannels for testing versions - The version name and changelog will be taken from the common
NAMEandDESCRIPTIONvariables - You can use the common
GAME_VERSIONSvariable to set versions for all platforms at once - If your plugin supports multiple platforms (Paper, Velocity, Waterfall), list them all in
HANGAR_PLATFORM