Skip to content

BED-10186: Fix GHCR release failure from cache export - #88

Merged
jaredcatkinson merged 1 commit into
mainfrom
fix/BED-10186-ghcr-cache-export
Oct 22, 2026
Merged

jaredcatkinson merged 1 commit into
mainfrom
fix/BED-10186-ghcr-cache-export

Conversation

@jaredcatkinson

@jaredcatkinson jaredcatkinson commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

The first GHCR release from #86 failed after building the CLI images because GitHub Actions cache export returned failed to reserve cache, canceling publication. The merged-PR release run had read-only cache access; the enterprise matrix job was then canceled.

Remove the cache export from the container publishing step while retaining cache imports. This avoids attempting unsupported cache writes and leaves image builds, smoke tests, multi-architecture publication, SBOM generation, and the upstream-main release restrictions unchanged.

Ticket: BED-10186. Follow-up to #86.
Failed release: https://github.com/SpecterOps/openhound-github/actions/runs/39622783366

Validation:

  • Parsed the workflow YAML and verified both build steps retain cache imports without cache exports.
  • Verified multi-architecture push and SBOM settings remain enabled.
  • git diff --check passed.

GHCR publication must be verified by the release run after merge. The existing release flow will create a patch version for this fix/ branch.

Summary by CodeRabbit

  • Chores
    • Updated the container publishing process to stop exporting build cache. Existing cache imports remain unchanged. This is an internal workflow change and does not alter user-facing functionality.

@coderabbitai

coderabbitai Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 16f5f05a-40f3-4d79-beb3-c60018b736f3
📥 Commits

Reviewing files that changed from the base of the PR and between 359599e and 22f544e.

📒 Files selected for processing: 1
  • .github/workflows/publish-container.yml
💤 Files with no reviewable changes: 1
  • .github/workflows/publish-container.yml

Included review availability: This review used your included allowance. 4 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

Walkthrough

The container publish workflow no longer exports Buildx cache to GitHub Actions. It retains the target-specific cache import setting.

Changes

Container publish workflow

Layer / File(s) Summary
Build cache configuration
.github/workflows/publish-container.yml
The workflow no longer exports Buildx cache to GitHub Actions. The target-specific cache import remains.

Priority: ⬆️ High

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 22f54

No actionable issue is established with the cache configuration change. GHCR publication will be confirmed by the next release run.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the GHCR release failure and the cache export fix. It is concise and accurately describes the main change.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

A rabbit watched the cache flow by,
Then tucked the export out of sight.
The target cache still comes along,
While carrots wait beside the song.
One small change, and hops delight.

Comment @coderabbitai help to get the list of available commands.

@jaredcatkinson
jaredcatkinson merged commit e4ae9aa into main Oct 22, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
pypi — 22f544ef Deployed Oct 22, 2026 by jaredcatkinson via publish / build #62
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.

2 participants