Skip to content

Consolidate publish gating into gatekeeper workflow - #11

Merged
coffee-the-dev merged 3 commits into
mainfrom
t3code/consolidate-ci-workflows
Apr 18, 2026
Merged

coffee-the-dev merged 3 commits into
mainfrom
t3code/consolidate-ci-workflows

Conversation

@coffee-the-dev

Copy link
Copy Markdown
Contributor

Summary

  • Moved publishability detection into gatekeeper.yml so main-branch pushes decide whether release jobs should run.
  • Converted publish.yml into a reusable workflow_call workflow and removed its standalone push trigger and duplicate verification steps.
  • Tightened gatekeeper concurrency so non-main refs can still cancel in progress while main keeps publish-related runs isolated.
  • Added the publish job to gatekeeper job aggregation so overall CI status reflects release execution.

Testing

  • Not run (workflow-only change).
  • Reviewed updated job dependencies and if conditions for changes, detect-publishable, agw-client, release-surface, and publish.
  • Verified publish.yml now only exposes the npm publish job via workflow_call and retains the required id-token: write permission.

- Run publish detection from gatekeeper on main
- Convert publish.yml to a reusable workflow
- Preserve release-surface and AGW client verification before publish

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8c0b0a75c5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/gatekeeper.yml Outdated
- Set `contents: read` and `id-token: write` on the reusable publish job
- Allow gatekeeper to invoke the publish workflow with the required token scope
- Add the new `detect-publishable` job to gatekeeper dependencies
- Include its result in the workflow failure/cancellation check
@coffee-the-dev
coffee-the-dev merged commit ce5decf into main Apr 18, 2026
14 checks passed
@coffee-the-dev
coffee-the-dev deleted the t3code/consolidate-ci-workflows branch April 18, 2026 18:38
coffee-the-dev added a commit that referenced this pull request Apr 18, 2026
Resolve conflicts with main's PRs #9-#12 (publish build fix, root docs,
publish gating consolidation into gatekeeper, thirdweb adapter split).

- publish.yml: adopt main's workflow_call structure (#11 consolidation)
  while preserving this branch's switch to `changesets/action@v1` for
  publishing so GitHub releases are created alongside the GitHub-formatted
  changelog. Keep the `!./packages/contracts` build filter from main (#9).
- gatekeeper.yml: keep main's detect-publishable + reusable publish call
  orchestration, but grant `contents: write` to the publish job so the
  inherited permissions allow the reusable workflow to create GitHub
  releases.
- pnpm-lock.yaml: regenerated via `pnpm install` so the lockfile reflects
  both main's new `@abstract-foundation/agw-thirdweb` workspace and this
  branch's `@changesets/changelog-github` dev dependency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant