Skip to content

Conversation

@nikw9944
Copy link
Contributor

@nikw9944 nikw9944 commented Feb 2, 2026

Summary of Changes

  • ci: github workflow that promotes component packages from cloudsmith doublezero-testnet repo to doublezero repo

Testing Verification

  • Tested by hand in github action runner

@nikw9944 nikw9944 linked an issue Feb 2, 2026 that may be closed by this pull request
@nikw9944 nikw9944 self-assigned this Feb 2, 2026
@nikw9944 nikw9944 marked this pull request as ready for review February 2, 2026 17:50
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the GitHub Actions workflow for promoting component packages from the Cloudsmith doublezero-testnet repository to the doublezero repository. The workflow now handles version input more flexibly and supports both RPM and DEB package formats.

Changes:

  • Updated version input description to remove the -1 suffix example
  • Uncommented all component packages in the expected packages list
  • Added logic to handle both RPM (version X.Y.Z) and DEB (version X.Y.Z-1) package formats by querying and merging results from both

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@packethog
Copy link
Contributor

If we just promote the package from the testnet repo, are we missing out on an opportunity to include an env-specific unit file in the package itself so users don't need to add overrides?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use separate doublezero-testnet Cloudsmith repo for testnet

3 participants