feat(ci): dispatch lock-update event to nix-ai on release#44
Merged
Conversation
JacobPEvans-personal
force-pushed
the
feat/dispatch-lock-updates
branch
from
12a866d to
d9cf900
Compare
After a nix-claude-code release is published, notify dryvist/nix-ai via repository_dispatch so it bumps its nix-claude-code flake input without waiting for the next Renovate lockFileMaintenance window (~Mon/Thu). The dispatch uses the GitHub App token scoped to nix-ai. nix-ai's own update-flake-input receiver and dispatch-to-nix-darwin workflows complete the two-hop propagation chain. Assisted-by: Claude:claude-opus-4-8
JacobPEvans-personal
force-pushed
the
feat/dispatch-lock-updates
branch
from
d9cf900 to
337526f
Compare
Replace the 41-line inline job with a 3-line call to the new reusable workflow in dryvist/.github. All logic (matrix fan-out, App-token mint, cross-repo dispatch) now lives in one place. Depends on: dryvist/.github adding _dispatch-flake-consumers.yml@main Refs: dryvist/.github#21 Assisted-by: Claude:claude-opus-4-8
This was referenced Jun 2, 2026
JacobPEvans-personal
added a commit
to dryvist/.github
that referenced
this pull request
Jun 2, 2026
Centralises the flake-consumer dispatch sender so every upstream repo that needs to notify downstream consumers on a release (or flake.lock push) can use a ~9-line caller instead of duplicating the full 41-line token-mint + matrix-dispatch job. Mirrors the conventions of the sibling _update-flake-input.yml: - @V3 create-github-app-token, vars.GH_APP_CLIENT_ID / GH_APP_PRIVATE_KEY - env-var injection guards on all run: steps - permissions: {} at top level, contents:read at job level - uses ${GITHUB_REPOSITORY_OWNER} instead of a hardcoded org name vars.DISPATCH_CONSUMERS and vars.GH_APP_CLIENT_ID resolve in the caller's context (workflow_call inherits caller vars), so they are read directly inside this workflow without input plumbing. GH_APP_PRIVATE_KEY is forwarded via `secrets: inherit` in each caller. The source_input default (${{ github.event.repository.name }}) resolves to the caller repo name, so callers typically need no `with:` block. Unblocks: dryvist/nix-claude-code#44, dryvist/nix-ai#869 Assisted-by: Claude:claude-opus-4-8
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
1 participant
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
dispatch-lock-updates.yml— fires arepository_dispatchtonix-aiimmediately after a nix-claude-code release is published, triggering the_update-flake-inputreusable workflow to bump the nix-claude-code input within minutes. This replaces the Mon/Thu Renovate lockfile maintenance window with event-driven updates.Changes
.github/workflows/dispatch-lock-updates.yml— thinworkflow_callcaller ofdryvist/.github/_dispatch-flake-consumers.yml@main; keeps thereleasetrigger and theDISPATCH_CONSUMERSrepo variable (["nix-ai"]); all dispatch logic now lives centrallygh apicallContext
Part of the event-driven flake-lock propagation chain:
Depends on (merge first): dryvist/.github#21 (
_dispatch-flake-consumers.yml@main)Refs: dryvist/.github#21, dryvist/nix-ai#869, dryvist/nix-darwin#1174
Test Plan
@main)nix flake checkpasses in this worktree (static)repository_dispatchfires to nix-aiupdate-flake-input.ymlreceives and processes the event🤖 Generated with Claude Code