Skip to content

Release documentation index updates - #106

Merged
ChiragAgg5k merged 1 commit into
mainfrom
chore/release-docs-refresh
Aug 16, 2026
Merged

Release documentation index updates#106
ChiragAgg5k merged 1 commit into
mainfrom
chore/release-docs-refresh

Conversation

@ChiragAgg5k

Copy link
Copy Markdown
Member

Summary

  • create the next patch release whenever the daily docs index changes
  • dispatch package publishing and production deployment explicitly because releases created with GITHUB_TOKEN do not trigger follow-on workflows
  • add validated release-tag inputs to the publish and production workflows
docs changed → commit → patch release → publish + production
no changes    → no commit or release

Test plan

  • actionlint .github/workflows/*.yml
  • parsed all workflow files with PyYAML
  • verified vMAJOR.MINOR.PATCH derivation and validation paths

@greptile-apps

greptile-apps Bot commented Aug 16, 2026

Copy link
Copy Markdown

Greptile Summary

The PR turns documentation-index updates into patch releases and explicitly starts package publishing and production deployment, while adding validated manual tag inputs to the downstream workflows.

  • Adds release-tag inputs and semantic-version validation to publishing and production.
  • Creates a patch release after committing an updated documentation index.
  • Explicitly dispatches publishing and deployment because GITHUB_TOKEN-created release events do not start those workflows.
  • The new release pipeline lacks recovery when release creation or dispatch fails after the index commit is pushed.

Confidence Score: 4/5

The release automation should not merge until a failed release or downstream dispatch can resume after the documentation-index commit has already been pushed.

Release creation and two independent dispatch calls occur after the durable commit, but every downstream operation is gated on detecting a new index diff in the current run, leaving partial releases without automatic recovery.

Files Needing Attention: .github/workflows/update-docs-index.yml

Important Files Changed

Filename Overview
.github/workflows/update-docs-index.yml Adds commit outputs, patch-release creation, and explicit downstream dispatches, but post-push failures cannot be recovered by rerunning the workflow.
.github/workflows/publish.yml Adds a required manual release-tag input and consistently validates and uses it for package and registry publication.
.github/workflows/production.yml Adds an optional validated release-tag input while preserving SHA-based behavior for untagged manual deployments.

Fix all with Greploop

Fix All in Claude Code Fix All in Codex

Prompt To Fix All With AI
### Issue 1
.github/workflows/update-docs-index.yml:67
**Post-push failures cannot resume**

When release creation or either workflow dispatch fails after the index commit is pushed, rerunning the workflow finds no index change and skips every downstream step, leaving the update unreleased, unpublished, or undeployed until it is repaired manually.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "chore: release documentation index updat..." | Re-trigger Greptile


- name: Create patch release
id: release
if: steps.commit.outputs.changed == 'true'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Post-push failures cannot resume

When release creation or either workflow dispatch fails after the index commit is pushed, rerunning the workflow finds no index change and skips every downstream step, leaving the update unreleased, unpublished, or undeployed until it is repaired manually.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/update-docs-index.yml
Line: 67

Comment:
**Post-push failures cannot resume**

When release creation or either workflow dispatch fails after the index commit is pushed, rerunning the workflow finds no index change and skips every downstream step, leaving the update unreleased, unpublished, or undeployed until it is repaired manually.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Claude Code Fix in Codex

@ChiragAgg5k
ChiragAgg5k merged commit 0e85f30 into main Aug 16, 2026
5 checks passed
@ChiragAgg5k
ChiragAgg5k deleted the chore/release-docs-refresh branch August 16, 2026 11:13
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