GitHub Packages

Push or pull Docker, Maven, and NuGet packages within CI/CD pipelines. Package type auto-aligns with your build step — no manual type configuration required.DockerMavenNuGetAuto-aligned✦All package transfer operations are logged in Pipeline Execution Logs for full traceability and compliance auditing.

Prerequisites

• GitHub integration configured and registered in Opsera Tool Registry

• Correct read/write permissions set on the GitHub repository for package operations

• A build step (Maven / Docker / NuGet) already configured in the pipeline

Pipeline setup

1

Configure a build step first

Add and configure your Maven, Docker, or NuGet build step. The Package Type in the GitHub Packages step will auto-populate from this step's configuration.

2

Add GitHub Packages step

Click +. Step Setup: Tool = GitHub Packages. Toggle step enabled, enter a name, set Dependencies to the preceding build step. Save.

3

Configure step settings

Select GitHub Tool from Tool Registry. Package Type is auto-filled. Set Package Name and Package Version (e.g. 1.0.0 or latest). Save.

4

Monitor transfer operations

Navigate to Summary → Pipeline Logs → Console Logs for transfer details, or Task Update Received for AI-generated summaries.

Points to remember

• Package type is auto-populated from the build step and cannot be changed manually — this prevents misconfiguration and ensures consistency across the pipeline.

• Package visibility is inherited from the GitHub repository — public repos produce public packages, private repos produce private packages.

• You can configure the step to pull dependencies before a build, or push artifacts after — both directions are supported.Uselatestas the version tag only for the most recently validated version — avoid using it for production deployments where exact version traceability is required.