Repository navigation
ci: weekly macOS and Windows leg; docs: scope split; register release.yml - #1
Merged
Merged
Conversation
dbpantry and mesobia ship binaries for macOS and Windows, so cloudkit has to build and pass there. Pull requests keep testing on Linux only.
…se.yml Managed-database administration stays with the consumer and descriptors support writes (mesobia ADR 0046 in the design record). release.yml changes so its merge registers the dispatch-only workflow, which the first push did not.
imanimanyara
changed the title
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
cross-osjob (macOS and Windows,make ciwith the race detector) runs weekly and on dispatch; pull requests keep testing on Linux only. It was proven by one dispatch on this branch.docs/architecture.mdnow states the split the owner settled: cloudkit finds and connects to managed databases but never administers them (that stays in mesobia's engine adapters), and REST descriptors, still planned, support writes behind signing or explicit enablement, plans against live state, typed destroy confirmation and the contract suite.release.yml. GitHub did not register the dispatch-only release workflow from the first push, so a dispatch would answer 404. Changing the file here means its merge registers it.docs/release.mdgains a step-0 check.This is also the repository's first CI run: the
Initial releasepush tomainstarted none, because CI triggers onpull_request, dispatch and the weekly schedule only.Checks
make ciand golangci-lint pass locallyCHANGELOG.mdhas[Unreleased]entries