ci: [pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.15.16 → v0.15.17
• github.com/pre-commit/mirrors-eslint: v10.4.1 → v10.5.0

[myakove-bot]

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

Note: You are an auto-verified user. Your PRs will be automatically verified and may be auto-merged when all requirements are met.

🔄 Automatic Actions

• Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
• Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
• Issue Creation: Disabled for this repository
• Pre-commit Checks: pre-commit runs automatically if .pre-commit-config.yaml exists
• Branch Labeling: Branch-specific labels are applied to track the target branch
• Auto-verification: Auto-verified users have their PRs automatically marked as verified
• Labels: All label categories are enabled (default configuration)

📋 Available Commands

PR Status Management

• /wip - Mark PR as work in progress (adds WIP: prefix to title)
• /wip cancel - Remove work in progress status
• /hold - Block PR merging (approvers only)
• /hold cancel - Unblock PR merging
• /verified - Mark PR as verified
• /verified cancel - Remove verification status
• /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
• /regenerate-welcome - Regenerate this welcome message
• /security-override - Set security check runs to pass (maintainers only)
• /security-override cancel - Re-run security checks

Review & Approval

• /lgtm - Approve changes (looks good to me)
• /approve - Approve PR (approvers only)
• /automerge - Enable automatic merging when all requirements are met (maintainers and approvers only)
• /assign-reviewers - Assign reviewers based on OWNERS file
• /assign-reviewer @username - Assign specific reviewer
• /check-can-merge - Check if PR meets merge requirements

Testing & Validation

• /retest tox - Run Python test suite with tox
• /retest build-container - Rebuild and test container image
• /retest python-module-install - Test Python package installation
• /retest pre-commit - Run pre-commit hooks and checks
• /retest conventional-title - Validate commit message format
• /retest all - Run all available tests

Container Operations

• /build-and-push-container - Build and push container image (tagged with PR number)
  • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

• /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
  • Multiple branches: /cherry-pick branch1 branch2 branch3
• /cherry-pick-retry <branch> - Retry a failed cherry-pick (merged PRs only)

Branch Management

• /rebase - Rebase this PR branch onto its base branch

Label Management

• /<label-name> - Add a label to the PR
• /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

1. Approval: /approve from at least one approver
2. LGTM Count: Minimum 1 /lgtm from reviewers
3. Status Checks: All required status checks must pass
4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

• myakove
• rnetser

Reviewers:

• myakove
• rnetser

Available Labels

• hold
• verified
• wip
• lgtm
• approve
• automerge

AI Features

• Conventional Title: Mode: fix (claude/claude-opus-4-6[1m])
• Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6[1m])
• Test Oracle: Triggers: approved (claude/claude-opus-4-6[1m]); /test-oracle can be used anytime

Security Checks

• Suspicious Path Detection: Monitors paths: .claude/, .vscode/, .cursor/, .devcontainer/, .pi/, .github/workflows/, .github/actions/
• Committer Identity Check: Verifies last committer matches PR author
• Mandatory: Security checks block merge (use /security-override to bypass — maintainers only)

💡 Tips

• WIP Status: Use /wip when your PR is not ready for review
• Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
• Cherry-picking: Cherry-pick labels are processed when the PR is merged
• Container Builds: Container images are automatically tagged with the PR number
• Permission Levels: Some commands require approver permissions
• Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

[rnetser]

/approve
/lgtm

[myakove-bot]

Tests to Run

The following tests should be run to verify this PR:

No tests need to run for this PR. The changes do not appear to affect any testable code paths.

Summary

• 0 test files recommended (0 critical, 0 standard)
• AI Provider: Claude (claude-opus-4-6[1m])

[myakove-bot]

Clean rebase detected — no code changes compared to previous head (0cb76f9).
The following labels were preserved: verified, approved-rnetser, lgtm-rnetser.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 24 rules

1. Stale hook revs docs 🐞 Bug ⚙ Maintainability

Description

docs/testing-and-maintenance.md (and its checked-in HTML/text mirrors) includes a "trimmed excerpt"
of .pre-commit-config.yaml with specific ruff/eslint rev values that no longer match the actual
.pre-commit-config.yaml after this PR. This can mislead contributors trying to reproduce CI/local
pre-commit behavior when debugging lint/format failures.

Code

.pre-commit-config.yaml[44]

+    rev: v0.15.17

Relevance

⭐ Low

Many pre-commit autoupdate PRs only change .pre-commit-config.yaml, leaving docs excerpt to drift
(e.g., PRs 1099, 1105).

PR-#1047
PR-#1099
PR-#1105

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The updated hook revs in .pre-commit-config.yaml (ruff v0.15.17, eslint mirror v10.5.0) do not
match the versions shown in the docs excerpt (ruff v0.15.6, eslint mirror v10.0.3), and those
outdated values are present in the checked-in Markdown, HTML, and llms text.

.pre-commit-config.yaml[43-47]
.pre-commit-config.yaml[62-66]
docs/testing-and-maintenance.md[194-228]
docs/testing-and-maintenance.html[448-482]
docs/llms-full.txt[7801-7832]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The documentation includes hard-coded excerpts of `.pre-commit-config.yaml` with outdated `rev` values (e.g., ruff/eslint), which no longer match the real config after this PR’s hook bumps.

## Issue Context
This repo checks in both Markdown docs and generated/derived artifacts (HTML and `llms-full.txt`) that repeat the same excerpt; they should be updated together (or the excerpt should omit specific `rev` pins) to avoid future drift.

## Fix Focus Areas
- docs/testing-and-maintenance.md[194-228]
- docs/testing-and-maintenance.html[448-482]
- docs/llms-full.txt[7801-7832]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Previous review results

Review updated until commit f917fed

Results up to commit a1c882a

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Stale hook revs docs 🐞 Bug ⚙ Maintainability

Description

docs/testing-and-maintenance.md (and its checked-in HTML/text mirrors) includes a "trimmed excerpt"
of .pre-commit-config.yaml with specific ruff/eslint rev values that no longer match the actual
.pre-commit-config.yaml after this PR. This can mislead contributors trying to reproduce CI/local
pre-commit behavior when debugging lint/format failures.

Code

.pre-commit-config.yaml[44]

+    rev: v0.15.17

Relevance

⭐ Low

Many pre-commit autoupdate PRs only change .pre-commit-config.yaml, leaving docs excerpt to drift
(e.g., PRs 1099, 1105).

PR-#1047
PR-#1099
PR-#1105

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The updated hook revs in .pre-commit-config.yaml (ruff v0.15.17, eslint mirror v10.5.0) do not
match the versions shown in the docs excerpt (ruff v0.15.6, eslint mirror v10.0.3), and those
outdated values are present in the checked-in Markdown, HTML, and llms text.

.pre-commit-config.yaml[43-47]
.pre-commit-config.yaml[62-66]
docs/testing-and-maintenance.md[194-228]
docs/testing-and-maintenance.html[448-482]
docs/llms-full.txt[7801-7832]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The documentation includes hard-coded excerpts of `.pre-commit-config.yaml` with outdated `rev` values (e.g., ruff/eslint), which no longer match the real config after this PR’s hook bumps.

## Issue Context
This repo checks in both Markdown docs and generated/derived artifacts (HTML and `llms-full.txt`) that repeat the same excerpt; they should be updated together (or the excerpt should omit specific `rev` pins) to avoid future drift.

## Fix Focus Areas
- docs/testing-and-maintenance.md[194-228]
- docs/testing-and-maintenance.html[448-482]
- docs/llms-full.txt[7801-7832]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[myakove-bot]

Clean rebase detected — no code changes compared to previous head (a1c882a).
The following labels were preserved: verified, approved-rnetser, lgtm-rnetser.

[qodo-code-review]

Code review by qodo was updated up to the latest commit f917fed

[myakove-bot]

New container for ghcr.io/myk-org/github-webhook-server:latest published