Skip to content

chore(ci): keep CLI release builds uncached - #4190

Open
strantalis wants to merge 1 commit into
mainfrom
codex/bdd-release-cache
Open

strantalis wants to merge 1 commit into
mainfrom
codex/bdd-release-cache

Conversation

@strantalis

@strantalis strantalis commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Stack merge order: release cache policy → shared BDD setup and Go cache → readiness polling → Docker cache.

Proposed Changes

The CLI release workflow leaves setup-go caching enabled by default while publishing binaries with a write-capable token. Disable that cache so published binaries are compiled from fresh dependency and compiler state. Container release builds already have no GitHub Actions layer-cache import and disable the Buildx binary cache.

This is the foundation of the BDD performance stack. CI caches remain available to test jobs; release dependency resolution, build commands, and publication stay unchanged.

Checklist

  • Reviewed Go and container release cache consumers
  • Validated the release workflow

Testing Instructions

actionlint and offline zizmor pass for .github/workflows/release-otdfctl.yaml, with zero findings. git diff --check passes. A real release was not run.

Signed-off-by: strantalis <strantalis@virtru.com>
@coderabbitai

coderabbitai Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 58 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: da307b32-ab18-4106-ae15-29aad5c8b11c
📥 Commits

Reviewing files that changed from the base of the PR and between 09a7d47 and d2dc916.

📒 Files selected for processing (1)
  • .github/workflows/release-otdfctl.yaml
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions github-actions Bot added the comp:ci Github Actions Work label Oct 7, 2026
@strantalis
strantalis added this pull request to stack #4191 October 7, 2026 11:24
@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor
Benchmark results, click to expand

Bulk Benchmark Results

Metric Value
Total Decrypts 100
Successful Decrypts 100
Failed Decrypts 0
Total Time 342.912383ms
Throughput 291.62 requests/second

TDF3 Benchmark Results

Metric Value
Total Requests 5000
Successful Requests 5000
Failed Requests 0
Concurrent Requests 50
Total Time 35.212372083s
Average Latency 351.549736ms
Throughput 142.00 requests/second

@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

⚠️ Govulncheck found vulnerabilities ⚠️

The following modules have known vulnerabilities:

  • otdfctl
  • service
  • tests-bdd

See the workflow run for details.

@strantalis
strantalis marked this pull request as ready for review October 7, 2026 12:32
@strantalis
strantalis requested review from a team as code owners October 7, 2026 12:32

@jakedoublev jakedoublev left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp:ci Github Actions Work size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants