Skip to content

Skip RPM repositories freshness check on unrelated PRs#239

Open
rhartman93 wants to merge 1 commit into
mainfrom
skip-rpm-freshness-check-on-unrelated-prs
Open

Skip RPM repositories freshness check on unrelated PRs#239
rhartman93 wants to merge 1 commit into
mainfrom
skip-rpm-freshness-check-on-unrelated-prs

Conversation

@rhartman93

Copy link
Copy Markdown
Contributor

Summary

  • The verify-data CI job fetches the remote repository-to-cpe.json on every PR and diffs it against local known_rpm_repositories.yml. If the remote source was updated since the last scheduled sync, unrelated PRs fail.
  • This change skips the RPM freshness check unless the PR modifies RPM repository-related files (known_rpm_repositories.yml, extra_rpm_repositories.yml, suppressed_rpm_repositories.yml, or the render/update scripts).
  • The ec validate policy and ec validate input checks continue to run on every PR as before.
  • The scheduled update_rpm_repositories workflow continues to keep the file in sync automatically.

Test plan

  • Open a PR that does not touch any RPM repository files — verify the freshness check is skipped with a log message
  • Open a PR that modifies data/known_rpm_repositories.yml — verify the freshness check runs as before

🤖 Generated with Claude Code

The verify-data check fetches the remote repository-to-cpe.json on every
PR and fails if the local known_rpm_repositories.yml is stale. This causes
unrelated PRs to fail when the remote source is updated between scheduled
syncs. Only run this check when RPM repository files are part of the change.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rhartman93 rhartman93 requested a review from ralphbean as a code owner July 1, 2026 17:15
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