Propagate changes from main into development

[github-actions]

Automated PR to propagate changes from main into development.

Triggered by push to main.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[Copilot]

Pull request overview

This automated propagation PR brings workflow updates from main into development, specifically adjusting the GeoLite2 checksum update workflow scheduling and its generated messaging.

Changes:

• Move the scheduled GeoLite2 checksum check from Mondays to Sundays (02:00 UTC).
• Update workflow-generated PR/issue text to reflect the new Sunday schedule.
• Set the PR base branch to development for the checksum update PRs.

[Copilot]

base: development is set for create-pull-request, but the workflow checks out the default ref (for schedule, GitHub runs on the default branch). If the default branch is main, the PR branch will be created from main and then opened against development, potentially producing a large PR containing all main→development differences (not just the checksum update). To keep the PR scoped, either check out development explicitly (e.g., set actions/checkout ref: development) when using base: development, or remove base so the PR targets the checked-out branch.

Suggested change

base: development

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1485

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	4
🟢 Low	0
Total	4

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!