chore: trigger axi npm package build on CLI release (CLI-1696) - #7118
Merged
Conversation
Adds axi as a 4th target alongside snyk-images/scoop-snyk/homebrew-tap
in trigger-distribution-channels, reusing the existing
trigger_repository_event helper (repository_dispatch, event_type
cli_release, payload {version, release_channel}). axi's
build-on-cli-release.yml already listens for this event.
CLI-1696
✅ 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. |
PeterSchafer
approved these changes
Aug 12, 2026
nick-y-snyk
enabled auto-merge
August 12, 2026 14:30
nick-y-snyk
disabled auto-merge
August 12, 2026 14:33
PR Reviewer Guide 🔍
|
Contributor
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
2 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.
What does this PR do?
Adds
axias a 4th target intrigger-distribution-channels, alongsidesnyk-images,scoop-snyk, andhomebrew-tap. Reuses the existingtrigger_repository_eventhelper — fires arepository_dispatchwithevent_type: cli_releaseandclient_payload: {version, release_channel}at github.com/snyk/axi/dispatches.axi'sbuild-on-cli-release.ymlalready listens forcli_releaseand readsclient_payload.version/release_channelso rc/preview builds don't clobber the npmlatesttag.CLI-1696: create and publish the
@snyk/axinpm package, triggered by CLI releases.Where should the reviewer start?
trigger_repository_eventinrelease-scripts/upload-artifacts.sh— the new call is a straight copy of the existing snyk-images/scoop-snyk/homebrew-tap entries, just a different repo + event type.How should this be manually tested?
shellcheckclean. Simulated the JSON payload construction and confirmed it parses into the exactversion/release_channelkeys axi's workflow reads.Live end-to-end validated:
@snyk/axi@0.1.0has been bootstrap-published (npm requires an initial token-based publish before Trusted Publishing can be configured). axi's OIDC trusted-publishing workflow itself was separately dry-run tested end-to-end on a disposable package (@nick-snyk/axi-test) before landing, including the actualnpm publishstep succeeding via GitHub Actions OIDC. Trusted Publisher config for@snyk/axiis pending setup by someone with npm org access; this PR's dispatch call works independently of that.What's the product update that needs to be communicated to CLI users?
None — internal release plumbing, no user-facing change.
Risk assessment
Low.
trigger_repository_eventfailures are caught and logged, non-blocking to the rest of the release (per its existing docstring); a broken/missing axi dispatch does not fail the CLI release itself.Supersedes #7117 (opened from a fork before I had direct write access to this repo).