zeroclaw/.github/workflows
Argenis 6463bc84b0
fix(ci): sync tweet and README after all release artifacts are published (#3531)
The tweet was firing on `release: published` immediately when the GitHub
Release was created, but Docker push, crates.io publish, and website
redeploy were still in-flight. This meant users saw the tweet before
they could actually pull the new Docker image or install from crates.io.

Convert tweet-release.yml and sync-readme.yml to reusable workflows
(workflow_call) and call them as the final jobs in both release
pipelines, gated on completion of docker, crates-io, and
redeploy-website jobs.

Before: gh release create → tweet fires immediately (race condition)
After:  gh release create → docker + crates + website → tweet + readme
2026-03-14 21:19:56 -04:00
..
checks-on-pr.yml ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -04:00
ci-run.yml ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -04:00
cross-platform-build-manual.yml chore(deps): bump actions/download-artifact from 4 to 8 2026-03-11 04:30:08 -04:00
master-branch-flow.md ci: add x86_64-pc-windows-msvc to build matrix (#3449) 2026-03-13 21:45:08 -04:00
publish-crates-auto.yml feat: auto-sync crates.io on version bump 2026-03-14 13:28:52 -04:00
publish-crates.yml fix: use --no-verify and clean web source to prevent build.rs from re-running npm 2026-03-14 13:05:03 -04:00
README.md chore: update .gitignore, CODEOWNERS, and dependabot configuration 2026-03-07 21:05:23 -05:00
release-beta-on-push.yml fix(ci): sync tweet and README after all release artifacts are published (#3531) 2026-03-14 21:19:56 -04:00
release-stable-manual.yml fix(ci): sync tweet and README after all release artifacts are published (#3531) 2026-03-14 21:19:56 -04:00
sync-readme.yml fix(ci): sync tweet and README after all release artifacts are published (#3531) 2026-03-14 21:19:56 -04:00
tweet-release.yml fix(ci): sync tweet and README after all release artifacts are published (#3531) 2026-03-14 21:19:56 -04:00

Workflow Directory Layout

GitHub Actions only loads workflow entry files from:

  • .github/workflows/*.yml
  • .github/workflows/*.yaml

Subdirectories are not valid locations for workflow entry files.

Repository convention:

  1. Keep runnable workflow entry files at .github/workflows/ root.
  2. Keep cross-tooling/local CI scripts under dev/ or scripts/ci/ when used outside Actions.

Workflow behavior documentation in this directory:

  • .github/workflows/master-branch-flow.md