Skip to content

Matched advisory candidates (shard 39) - #2177

Open
BrewTestBot wants to merge 1 commit into
mainfrom
matched-advisories-39
Open

BrewTestBot wants to merge 1 commit into
mainfrom
matched-advisories-39

Conversation

@BrewTestBot

Copy link
Copy Markdown
Contributor

Automated candidates via brew advisory-match --formula-list (planned workers) --new-history, sharded by formula (SHA-256 bucket 39). See CONTRIBUTING.md for the review checklist.

Run and review artifacts: https://github.com/Homebrew/advisory-database/actions/runs/44487676220

@coderabbitai

coderabbitai Bot commented Nov 19, 2026

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Updated the advisory record’s modification date and added an upstream identifier, keeping the published advisory details current.

The advisory record adds upstream identifier PYSEC-2026-4389 and updates its modified timestamp to 2026-11-19T10:58:40Z.

Changes: Advisory metadata update

Layer / File(s) Summary
Update advisory metadata
advisories/BREW-pferd-GHSA-2g87-pp6c-29x5.json
The record adds PYSEC-2026-4389 to its upstream identifiers and updates the modified timestamp. Existing identifiers remain.
Merge Risk: Minimal · up to 938bf

This automated advisory metadata update adds an upstream identifier and refreshes the modified date. No merge-blocking risk was found.

Pre-merge checks: Passed 3 · Inconclusive 1

Failed Failed checks: 1 inconclusive

Check name Status Explanation Resolution
Title check Inconclusive The title "Matched advisory candidates (shard 39)" is generic. It names the kind of change (matched advisory candidates) and a shard number, but not the advisory changed or the affected formula. The d… Name the main change in the title. For example, reference the advisory or formula updated, such as "Update BREW-pferd-GHSA-2g87-pp6c-29x5 with PYSEC-2026-4389". Keep the shard reference if the team needs it.
Passed Passed checks: 3 passed

Check name Status Explanation
Description check Passed The description states that the changes are automated advisory candidates from brew advisory-match, sharded by formula with SHA-256 bucket 39. It links the review checklist and run artifacts. This rel…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description states that the changes are automated advisory candidates from brew advisory-match, sharded by formula with SHA-256 bucket 39. It links the review checklist and run artifacts. This relates to the changeset, which contains automated advisory record updates, so the check passes.

Full details: Title check

Explanation

The title "Matched advisory candidates (shard 39)" is generic. It names the kind of change (matched advisory candidates) and a shard number, but not the advisory changed or the affected formula. The diff only modifies one advisory record (BREW-pferd-GHSA-2g87-pp6c-29x5.json) to update its modified date and add PYSEC-2026-4389 as an upstream identifier. The title is related to the changeset, but it is vague about the actual change. It is not off-topic, so it does not fail.

Resolution

Name the main change in the title. For example, reference the advisory or formula updated, such as "Update BREW-pferd-GHSA-2g87-pp6c-29x5 with PYSEC-2026-4389". Keep the shard reference if the team needs it.

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between a2584ad and 938bf5c.

Files selected for processing: 1

  • advisories/BREW-pferd-GHSA-2g87-pp6c-29x5.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

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