Repository navigation
build: update pinned ci-tools to bdfe993 - #248
Merged
Merged
Conversation
The pin was twelve commits and close to six months behind, so several merged fixes were not the ones running here. What changes: the changelog workflow keeps one self-updating pull request instead of opening a new one per run, skips release commits rather than failing on them, and serialises its own runs; create-pr no longer builds git commands through a shell and refuses a branch_name equal to the base branch; Commitizen is pinned rather than upgraded on every run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
All reviewed pins are updated to the verified commit with no unresolved issues.
Pull request overview
Updates pinned ci-tools references to commit bdfe993, bringing recent CI workflow fixes and security improvements.
Changes:
- Updates project-docs PR action pin.
- Updates changelog workflow pin.
- Updates Commitizen workflow pins.
File summaries
| File | Description |
|---|---|
.github/workflows/pull-project-docs.yml |
Updates the create-pr action pin. |
.github/workflows/generate-changelog.yml |
Updates the changelog workflow pin. |
.github/workflows/commitizen.yml |
Updates Commitizen workflow pins. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
lwshang
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pinned
ci-toolscommit was twelve commits and close to six months behind, so several merged fixes were not the ones running here.Behaviour changes
main, and closes it once there is nothing left to propose.^chore:[[:space:]]release([[:space:]]|$)is skipped rather than failing when Commitizen finds nothing to add.create-prno longer builds git commands through a shell, so a branch name, commit message or author value cannot be read as shell syntax. It also refuses abranch_nameequal tobase_branch_name, and ends option parsing before the branch ongit push.4.18.1rather than upgraded on every run.For the reviewer
pull-project-docsis unaffected:reuse_branchdefaults tofalseon the action, so docs-update pull requests keep their randomly suffixed branches. Switching that on needs a per-project branch name first — six projects sharebuild/docs-update, and each run resets tomainafter emptying only its ownpublic/<subdirectory>, so reuse would discard another project's unmerged update.Verified before bumping that all four referenced actions and workflows exist at the new commit and still declare every input and secret this repository passes.
🤖 Generated with Claude Code