Repository navigation
ci(release): notify the docs repo so CLI releases get release notes - #46
Merged
Merged
Conversation
Add a notify-docs job that sends the same `release` repository_dispatch to dualentry/docs that backend and frontend send through release-cycle, with repo `dualentry-cli` and the release tag. It runs after the binaries upload, skips pre-releases, and can't fail the release.
a-c-wagner
commented
Nov 9, 2026
xSAVIKx
approved these changes
Nov 9, 2026
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
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
CLI releases don't get release notes on the docs site today, because nothing tells the docs repo a CLI release happened. Backend and frontend send a
releaserepository dispatch todualentry/docswhen they publish; this adds the same dispatch to the CLI release workflow so v0.1.22 onward gets notes automatically.The docs side is already in place: dualentry/docs#1156 limits the wiki rebuild to backend and frontend, so a CLI release only produces release notes.
Changes
notify-docsjob in.github/workflows/release.yml, afterupload:dualentry/docswithcontents: write, using the same app credentials the workflow already uses;event_type: releasewithclient_payload{repo: dualentry-cli, release_tag: <tag>};continue-on-error: true, so a docs-side problem never fails a release;permissions: {}for the job's ownGITHUB_TOKEN.Test plan
actionlintpasses on.github/workflows/release.yml.notify-docsjob succeeds and a "Process Release" run starts in dualentry/docs withrepo: dualentry-cli.Artifacts
No
src/changes, so nothing to run against the API.