Auto-update and release against new Chronicle versions#2324
Open
woksin wants to merge 2 commits into
Open
Conversation
React to a Chronicle release via repository_dispatch (chronicle-published): bump the Cratis.Chronicle, Cratis.Chronicle.AspNetCore and Cratis.Chronicle.Testing pins, run the full spec suite as a gate, and open a PR. On a green non-major bump auto-merge is enabled so the existing publish flow releases Arc against a verified-compatible Chronicle — turning silent downstream breakage into an Arc-side red build instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the single-package flat-container poll with a restore-retry loop: dotnet restore is the actual operation that must succeed, so retrying it covers all three Chronicle packages, isn't fooled by CDN edge-node cache divergence, and clears the HTTP cache between attempts to defeat cached negative lookups. Build now runs with --no-restore. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Added
Chronicle Publishedworkflow that reacts to a Chronicle release, updates theCratis.Chronicle,Cratis.Chronicle.AspNetCoreandCratis.Chronicle.Testingpackage versions, verifies the update against the full spec suite, and opens a pull request — auto-merging (and thereby releasing Arc) when the specs pass on a non-major bump.Summary
Today, keeping Arc's Chronicle dependency current is manual. Because Arc publishes with an open-ended
>= xdependency, consumers can pull a Chronicle newer than anything Arc has tested — and a breaking Chronicle change then surfaces in their build, not ours.This workflow closes that gap. When Chronicle publishes, it dispatches
chronicle-publishedto Arc (see the companion Chronicle PR). Arc waits for the new version to be available on NuGet, bumps the three pins, and runs every*.Specsproject as a gate:The net effect: the day Chronicle publishes, Arc either ships a verified release automatically or hands us a red PR — downstream consumers are never ahead of a Chronicle version Arc has actually tested.
Prerequisites (repo settings, not code): "Allow auto-merge" must be enabled, and the existing
PAT_WORKFLOWSsecret is used so the bump PR triggers CI and can be auto-merged.