Skip to content

Dispatch docs deploy after releases#84

Merged
dexcompiler merged 1 commit into
mainfrom
codex/release-docs-version-dispatch
May 16, 2026
Merged

Dispatch docs deploy after releases#84
dexcompiler merged 1 commit into
mainfrom
codex/release-docs-version-dispatch

Conversation

@dexcompiler
Copy link
Copy Markdown
Owner

Summary

  • let manual docs workflow dispatch accept an explicit version label
  • prevent versionless manual docs builds from deploying a dev label to Pages
  • have the release workflow dispatch and watch the docs workflow after the GitHub Release is created

Why

The main-merge docs deploy can run before the new GitHub Release exists, so it may resolve the previous release tag. Dispatching docs after the release is created removes that timing race.

Validation

  • npm run docs:build
  • git diff --check

Note: Ruby is not installed in this local environment, so YAML syntax is left to the GitHub Actions analyzer in CI.

@dexcompiler
Copy link
Copy Markdown
Owner Author

@copilot review this pr

Copy link
Copy Markdown
Contributor

Copilot AI commented May 16, 2026

@copilot review this pr

Reviewed the PR at cb602ea and ran validation locally (dotnet test tests/Clockworks.Tests.csproj -c Release --nologo, npm --prefix docs ci, npm --prefix docs run docs:build, git diff --check). I don’t see any blocking issues in the workflow changes.

@dexcompiler dexcompiler merged commit a57b92f into main May 16, 2026
7 checks passed
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.

2 participants