ci: join the autoupdate flow so releases stop needing a manual bump - #1
Merged
Merged
Conversation
Both publish only when someone bumps package.json by hand. Their release.yml is fine -- it fires on workflow_run after CI on main and its history shows that trigger working. What they lack is the flow that produces a version bump in the first place: neither has autoupdate.yml or claude.yml, and neither was in the template system at all. Adds configs for both, so they get the same weekly dependency update, patch bump, Claude compatibility fix and gated auto-merge as the other nine. Their existing release.yml then publishes on its own. Two mechanics were needed to fit repos that already own their CI: - SKIP_PR_CHECKS: no pr-checks.yml is generated for them. The existing test.yml (agent-web) and ci.yml (agent-web-react) stay authoritative. - The autoupdate "Trigger PR checks" step no longer hardcodes pr-checks.yml; it renders from `ci_workflows`, the key claude.yml already used. As a side effect `agent` now dispatches both of its gates (pr-checks.yml and test.yml) rather than only the first. Both are also in SKIP_RELEASE_ON_BUMP: they release through their own release.yml on CI success, not through a version-bump tag chain, so no release-on-version-bump.yml and no tag/deploy step is generated. Checks run before any publish, twice over: the merge gate requires every check run on the PR to be green, and release.yml then runs only on `workflow_run` of CI with conclusion == 'success'. Both repos' CI is a real suite -- typecheck, format:check, build, test, plus the demo build for agent-web-react. The other eight repos render byte-identical.
siarheidudko
marked this pull request as ready for review
August 8, 2026 08:30
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.
Rolls out from
siarheidudko/claude#6.Why
This package publishes only when someone bumps
package.jsonby hand.release.ymlis not the problem. It watchesworkflow_runofCIonmain— correct wiring — and its history shows the trigger working: runs #1–5 all fired viaworkflow_run; only the most recent (Aug 3) was manual.What is missing is the flow that produces a version bump. This repo has no
autoupdate.ymland noclaude.yml, and was not in the template system at all. Sorelease.ymlruns after every CI onmainand correctly skips, becauseSkip if version already on npmfinds nothing new.Changes
Adds
autoupdate.ymlandclaude.yml, generated from the shared templates:siarheidudko/autoupdater, withnpm run typecheck && npm run format:check && npm run build && npm testas the gate.release.ymlhas something to publish.@types/nodeis pinned out of updates, matching the sibling repos.No
pr-checks.ymlis added — the existingci.ymlstays the authoritative CI, andci_workflows: ["ci.yml"]points the flow at it. That means the Demo job gates the merge too, so a dependency update that breaks the Vite demo build blocks the release. Norelease-on-version-bump.ymleither: this repo releases throughrelease.ymlon CI success, which already works.deploy-demo.ymlis untouched.Checks run before any publish — twice
release.ymlruns only onworkflow_runof CI withconclusion == 'success'.ci.ymlis unchanged: Library (typecheck→format:check→build→test) plus Demo (build library → build demo).What changes for you
Dependency updates will merge and publish without review when everything is green. If you would rather keep a human in the loop, drop the merge step from
claude.ymland the wait-and-merge step fromautoupdate.yml— the PRs will still be opened and checked, just left for you.Generated by Claude Code