GitHub
682 incident problems in GitHub environments.
먼저 읽을 가이드
추천 문제
All problems (682)
CICD-1306A BuildKit push works manually on the runner but fails in automationA self-hosted runner pushes images successfully by hand and fails only inside the CI job using BuildKit or buildx.CI/CDIntermediate15 minProCICD-1296A cache migration to the new backend breaks one monorepoA monorepo upgrades cache actions and starts seeing odd dependency drift between package builds.CI/CDIntermediate15 minProCICD-1282A canceled deployment keeps every later release blockedA release job is manually canceled during an outage drill, and every subsequent deployment remains stuck in queued or waiting state.CI/CDIntermediate15 minProCICD-1272A checkout step fails only after repository ownership hardeningA self-hosted runner begins failing on fetch, submodule, or describe steps after a host hardening or container ownership change.CI/CDIntermediate15 minProCICD-1269A deployment job waits forever on environment approvalA deployment pipeline was refactored into reusable pieces and later one stage keeps waiting even though human approval already happened.CI/CDIntermediate15 minProCICD-1290A deployment reports the new image tag correctly but Kubernetes still rolls backA team standardizes image tags and suddenly deployments roll back despite successful image publication.CI/CDIntermediate15 minProCICD-1300A generated artifact downloads correctly but unzip fails only on Windows runnersA cross-platform workflow publishes one shared artifact and later only Windows jobs fail to unpack it.CI/CDIntermediate15 minProCICD-1315A registry retention cleanup removes a digest still referenced by a manifest listA registry cleanup policy appears safe until one platform begins failing pulls from a still-present multi-arch tag.CI/CDIntermediate15 minProCICD-1276A release job creates the image correctly but the deploy host still pulls the previous versionA release pipeline reports success and later the runtime still runs yesterday's image even though the registry contains the new one.CI/CDIntermediate15 minProCICD-1293A secrets: inherit rollout still breaks one reusable workflowOne shared deployment workflow works in some repos and fails in another after secret inheritance was adopted.CI/CDIntermediate15 minProCICD-1295A self-hosted runner builds once and then fails on rerunA self-hosted runner succeeds on first execution and later begins failing on rerun or retry flows.CI/CDIntermediate15 minProCICD-1280An artifact upload succeeds but the next matrix phase downloads the wrong oneA multi-env build and deploy flow looks fine in GitHub Actions, but staging and production artifacts are easy to confuse by name.CI/CDIntermediate15 minProCICD-120Release note automation rewrites the semantic version tag into a prerelease suffix and downstream promotion logic refuses the artifactThe published artifact exists, but the promotion controller rejects it because the computed version string no longer matches the expected stable pattern.CI/CDAdvanced15 minProCICD-1259setup-python works on hosted runners but fails on a self-hosted MacA self-hosted macOS runner starts failing only on language setup steps after an upgrade or user switch.CI/CDIntermediate15 minProCICD-134A dependency proxy serves a cached package manifest after the source package was revoked, and downstream builds keep resolving the unsafe versionUpstream fixed the issue, but the local acceleration layer preserved the vulnerable metadata view.CI/CDIntermediate16 minProCICD-1237A deployment gate reads the changelog successfully but still blocksA release pipeline derives approval logic from generated change metadata and later blocks only on unusually large releases.CI/CDIntermediate16 minProCICD-1284A deployment job can push images but cannot update the registry cacheA team adds registry-backed Buildx caching and only the cache step begins failing while the ordinary push still works.CI/CDIntermediate16 minProCICD-144A merge queue rebases the branch after tests pass, but the artifact fingerprint still reflects the pre-rebase commit and provenance checks reject the releaseThe code intent did not change much, yet artifact identity no longer matches the merge result the repository now points at.CI/CDIntermediate16 minProCICD-1232A monorepo path filter looks correct but one shared library change never triggers the deployA shared module changes and downstream services keep serving old logic because their deploy workflow never re-ran.CI/CDIntermediate16 minProCICD-210A release exception is approved while its audit evidence never reaches the archive during a failover rehearsalOperations can continue in the moment, yet the governance record for why it happened is incomplete. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate16 minPro