Skip to content

ci: auto-update documentation after releases#168

Closed
jd wants to merge 1 commit intomainfrom
devs/jd/ci/autodoc-on-release/Id86dc09a2e74c7b54e9b8418038878dfd3c6955e
Closed

ci: auto-update documentation after releases#168
jd wants to merge 1 commit intomainfrom
devs/jd/ci/autodoc-on-release/Id86dc09a2e74c7b54e9b8418038878dfd3c6955e

Conversation

@jd
Copy link
Copy Markdown
Member

@jd jd commented Apr 2, 2026

Add a workflow that regenerates README.md after each release
using tj-actions/auto-doc, then creates a PR with the updated
documentation. This prevents CI failures on subsequent PRs
caused by stale version references in the README.

Add a workflow that regenerates README.md after each release
using tj-actions/auto-doc, then creates a PR with the updated
documentation. This prevents CI failures on subsequent PRs
caused by stale version references in the README.

Change-Id: Id86dc09a2e74c7b54e9b8418038878dfd3c6955e
Copilot AI review requested due to automatic review settings April 2, 2026 14:48
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 2, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 🤖 Continuous Integration

This rule is failing.
  • all of:
    • check-success=all-greens

🔴 👀 Review Requirements

This rule is failing.
  • any of:
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[bot]

🔴 🔎 Reviews

This rule is failing.
  • #review-threads-unresolved = 0
  • #changes-requested-reviews-by = 0
  • #review-requested = 0

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 📕 PR description

Wonderful, this rule succeeded.
  • body ~= (?ms:.{48,})

@mergify mergify bot had a problem deploying to Mergify Merge Protections April 2, 2026 14:48 Failure
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a GitHub Actions workflow that automatically regenerates README.md documentation after a release is published and opens a PR with the changes, helping prevent CI failures caused by stale README version references.

Changes:

  • Introduces a new release.published-triggered workflow to run tj-actions/auto-doc.
  • Automatically opens a PR (branch named from the release tag) containing the regenerated documentation.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

runs-on: ubuntu-24.04
steps:
- name: Checkout
uses: actions/checkout@v6
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

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

actions/checkout is referenced as @v6 here, while the rest of the workflows mostly pin it to the patch version (actions/checkout@v6.0.2, e.g. .github/workflows/ci.yaml:21,74,115,153). Consider pinning this workflow to the same patch version for consistency and more deterministic runs.

Suggested change
uses: actions/checkout@v6
uses: actions/checkout@v6.0.2

Copilot uses AI. Check for mistakes.
@jd jd closed this Apr 2, 2026
@jd jd deleted the devs/jd/ci/autodoc-on-release/Id86dc09a2e74c7b54e9b8418038878dfd3c6955e branch April 2, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants