[rohilsurana]

Problem

A release tag runs the release workflow. The fast GoReleaser config pushes the raystack/frontier:latest Docker image. A patch release cut from release-v0-117-x would move latest from 0.118.0 back to 0.117.x.

Change

On this release branch only, .goreleaser-fast.yml no longer pushes the latest tag. The release still pushes raystack/frontier:<tag> and raystack/frontier:<tag>-amd64.

main is unchanged, so releases from main keep moving latest.

Notes

• The workflow also pushes raystack/frontier:dev on every tag. That is unchanged.
• This is for v0.117.2, which carries fix(organization): keep stored metadata when an update does not set it #2018.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
frontier	Ready	Preview	Oct 27, 2026 6:35am UTC

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: raystack/frontier
• Branch: ci/release-0-117-no-latest-tag
• File: .coderabbit.yaml
• Commit: 11cfaa0
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 0b46ae89-4e1d-43f1-8510-3b0e759a663e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coveralls]

Coverage Report for CI Build 40461945636

Warning

No base build found for commit ba1fe4a on release-v0-117-x.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 50.237%

Details

• Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	41117
Covered Lines:	20656
Line Coverage:	50.24%
Coverage Strength:	16.12 hits per line

---

💛 - Coveralls