Publish gate → default branch + docs/skills alignment + 0.2.1 baseline#48
Merged
Conversation
…0.2.0 (-> publishes 0.2.1)
- Publish gate: switch literal master/main to github.event.repository.default_branch
in both uv-ci.yml and the inline github_ci_uv.yml, so publish keys off the repo's
actual default branch (consistent with the github-pages job; correct for repos
whose default branch is named otherwise). Tests updated/added.
- Version baseline -> 0.2.0 so the CI auto-bump publishes 0.2.1.
- Docs/skills aligned with the two-layer secrets model + wads-secrets:
- wads-migrate SKILL.md: drop stale 'secrets: inherit' + curated-list claims;
document wads-secrets and the transport/env-policy split (this is the skill
that guides the upcoming fleet migration).
- README.md: add 'Configure Secrets' section + default-branch publish note.
- CLAUDE.md: replace legacy github_ci_publish_2025 references with uv-ci.yml/stub;
document export-ci-env + the validation-gated, default-branch publish.
- .gitignore: ignore .claude/scheduled_tasks.lock
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.
Pre-fleet-migration release. Three things:
1. Publish gates on the repo's actual default branch
Both
uv-ci.ymland the inlinegithub_ci_uv.ymlswitched the publishif:from a literalmaster || mainto:This matches the
github-pagesjob and is correct for repos whose default branch is neithermasternormain(which previously would never publish), and avoids publishing from a stray non-defaultmaster/mainbranch. Combined with the prior fix, publish now requires: default branch + validation green + not[skip ci]+ publishing enabled.test_workflow_gates.py/test_uv_workflow_template.pyupdated to pin it.2. Version baseline → 0.2.0 (publishes 0.2.1)
The CI auto-bump increments on publish, so setting the baseline to
0.2.0makes the next publish ship 0.2.1, as requested.3. Docs & skills aligned with the new wads way
For the upcoming migration of 10–20 repos, the guidance must be correct:
wads-migrateSKILL.md (the migration guide; symlinked into~/.claude/skills/): removed the stalesecrets: inheritclaim and the old "curated env-var list" text; documentedwads-secrets addand the transport-vs-env-policy two-layer model + new Secrets section.wads-secrets,[tool.wads.ci.env], the superset) and a note that publishing happens on the default branch only when validation passes.github_ci_publish_2025.ymlreferences with the stub/uv-ci.yml; documented theexport-ci-envstep and the validation-gated, default-branch publish flow.wads-ci-fixandwads-ci-sweepskills were reviewed and are already accurate.Full suite: 286 passed.