Draft
fix: handle disabled issues in monitor_libseccomp_releases workflow#2
Conversation
The check-release job was failing because the repository has disabled issues, but the workflow unconditionally attempted to create an issue when a new libseccomp version was detected. Changes: - Add a step to check if issues are enabled in the repository via the GitHub API - Skip issue creation and "check if issue exists" steps when issues are disabled - Add a warning step that emits a workflow warning when issues are disabled, so the notification is still surfaced without causing job failure
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job check-release
fix: handle disabled issues in monitor_libseccomp_releases workflow
Jul 16, 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.
Changes
tools/devctr/Dockerfile:v2.6.0→v2.6.1(resolves the immediate trigger)Check if issues are enabledstep: queriesGET /repos/{owner}/{repo}forhas_issuesbefore any issue-related stepshas_issues: bothCheck if issue existsandCreate issue for new releaseare skipped when issues are disabledWarn if issues are disabledstep: emits a::warning::annotation surfacing the available update without failing the jobReason
The
check-releasejob was failing with:The workflow unconditionally ran
gh issue createafter detecting a newer libseccomp release, with no guard for repositories that have the Issues feature disabled.License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.PR Checklist
tools/devtool checkbuild --allto verify that the PR passesbuild checks on all supported architectures.
tools/devtool checkstyleto verify that the PR passes theautomated style checks.
how they are solving the problem in a clear and encompassing way.
in the PR.
CHANGELOG.md.Runbook for Firecracker API changes.
integration tests.
TODO.rust-vmm.