gha - separate cloudsmith publishing in a new workflow #13682
Merged
+193
−49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this way wa can manually call it to publish release
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR extracts Cloudsmith package publishing into a separate, reusable workflow to enable manual publishing of releases (particularly for v1.8 patch releases). The new workflow downloads packages directly from GitHub releases rather than from workflow artifacts.
Key Changes:
- Creates a new standalone workflow for Cloudsmith publishing with manual trigger capability
- Updates the existing release workflow to call the new workflow instead of performing publishing inline
- Implements version resolution logic supporting "latest" and specific version/tag inputs
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/publish-cloudsmith.yml |
New workflow with manual dispatch support, version resolution, asset validation, and Cloudsmith publishing jobs |
.github/workflows/create-release.yml |
Refactored to call the new publish-cloudsmith workflow instead of performing publishing inline |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
Collaborator
Author
|
This require we do add rpm and deb assets to 1.8 though.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this way wa can manually call it to publish release
Aim is to start publishing v1.8 patch release there