feat: speed up release by prioritizing linux/amd64 #1323
+104
−12
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Pull Request Test Coverage Report for Build 20327187462Details
💛 - Coveralls |
Split GoReleaser into two stages: - Fast release: linux/amd64 binary + Docker image (what users wait for) - Full release: remaining platforms, appends to existing release Changes: - Add .goreleaser-fast.yml for linux/amd64 only - Update .goreleaser.yml to exclude linux/amd64 and use append mode - Split workflow into test -> release-fast -> release-full - Move tests to dedicated prerequisite job instead of GoReleaser hook 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Add `make test-quick` without -race and -count 2 flags - Use test-quick in release workflow to save ~2-3 minutes 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Tests already run on every PR via CI. No need to duplicate in release. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
whoAbhishekSah
force-pushed
the
feat/faster-linux-amd64-release
branch
from
76e4ebc to
8bed6fd
Compare
rsbh
approved these changes
Dec 22, 2025
Member
|
@whoAbhishekSah I think this makes the pipeline very complicated and very tactical. We should keep it streamlined. And try to improve it by optimizing the process and avoid creating silos. |
rohilsurana
approved these changes
Jan 13, 2026
Member
|
@ravisuhag we tried optimizing the build process and the best we could get with every sort of caching, removing tests, etc was 9 mins. I think we will still benefit from this approach and can apply same optimizations to this as well. |
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.
Speed up the release process by prioritizing linux/amd64 artifacts, which are what most users wait for.
Changes
.goreleaser-fast.yml- dedicated config for linux/amd64 binary, Docker image, and deb/rpm packages.goreleaser.yml- exclude linux/amd64 (handled by fast config), usemode: appendto add artifacts to existing releaseNew Workflow Structure
Job Details
devrelease-fast:latest,:tag,:tag-amd64), deb/rpm packagesrelease-fullrelease-fastPerformance Improvement
What's in the fast release (what users wait for)
:latest,:tag,:tag-amd64)What's deferred to full release
Test plan
raystack/frontier:latestis pushedrelease-fullappends remaining artifacts