Publication workflow

Add the publication workflows with these new goals:

• rc-download: Download artifacts from remote repositories to local staging
• rc-bundle: automates the bundle creation process for remote artifacts and local staging artifacts
• rc-upload: Upload bundle to staging area
• rc-sync: provides a complete orchestrated workflow that chains together RC goals (rc-download, rc-bundle, rc-sync) for end-to-end artifact synchronization with a remote repository. This workflow is designed for complex scenarios where artifacts need to be downloaded from remote repositories, processed, and published to Maven Central.

1.1.0

What's Changed

• feat: generate help mojo by @pzygielo in #2
• fix: remove unused parameter by @pzygielo in #3
• Extend rc-list goal with showArtifacts param by @senivam in #4
• Add new param central.bearerCreate to build bearer from settings.xml

New Contributors

• @pzygielo made their first contribution in #2
• @senivam made their first contribution in #4

Full Changelog: 1.0.0...1.1.0

1.0.0

First release that support these features:

• Authenticate with Bearer token (from CLI or Maven settings.xml)
• Upload artifact bundles to Central Portal with configurable publishing types
• Check if a component is published in Central
• Retrieve and display deployment status (state, errors, date)
• List all deployments for a namespace, including state, creation date, and errors per component
• Release (publish) a deployment if it is validated
• Drop (delete) a deployment by ID
• Drop all deployments in a namespace with central.removeAll
• Drop only deployments in FAILED state with central.removeFailedOnly (works with single, latest, or all deployments)
• Supports custom Central Portal API URL and serverId for token retrieval