fix: publish docker and package artifacts in release flow#199
Merged
chopratejas merged 4 commits intochopratejas:mainfrom Apr 20, 2026
Merged
Conversation
Call the Docker workflow from the release pipeline so Docker publishes in the same run, build npm tarballs alongside Python distributions, and attach those artifacts to the GitHub release page. Co-authored-by: Copilot <[email protected]>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Add a workflow-validation CI job that installs actionlint and act, checks the release and Docker workflows against checked-in event fixtures, and shares the same validation script developers can run locally. Co-authored-by: Copilot <[email protected]>
Fix workflow validation failures by wiring detect-version outputs into all release publish jobs, renaming the GitHub Packages skip variable to a valid Actions variable name, and adjusting the macOS PATH export for actionlint. Also make min_tokens_to_compress use token counting instead of whitespace splits so compact JSON tool outputs still compress after merging the latest main branch changes, and add a regression test for that path. Co-authored-by: Copilot <[email protected]>
Bring the branch onto upstream/main so GitHub validates the same merged compression code locally, and install act into PATH for the workflow-validation job. This keeps the compact-JSON compression regression fixed while making the shared validation script pass in CI. Co-authored-by: Copilot <[email protected]>
JerrettDavis
force-pushed
the
fix/release-publish-artifacts
branch
from
bc0a366 to
8a6579b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Validation
Why
The current release workflow can succeed without publishing Docker at all, and the GitHub release page ends up with no Python or npm artifacts. This change makes the GitHub release the place where Docker publication and release assets land together, alongside the remote package publishes.