[rohilsurana]

Problem

We need to cut v0.117.3 from release-v0-117-x, since production runs 0.117. A release tag currently does four things that treat the patch as the newest version, even though v0.119.0 is out:

• web-sdk.yml runs on every v*.*.* tag. It checks out main, not the tagged commit, gives that build the tag's version, and publishes it to npm. npm marks it latest. This happened for v0.117.2 on 2026-10-27, which published @raystack/frontier@0.117.2 built from main and moved latest until v0.119.0 was published 23 minutes later.
• GoReleaser pushes the frontier formula to raystack/homebrew-tap and the manifest to raystack/scoop-bucket. v0.117.2 rolled both back from 0.118.0 until v0.119.0 moved them forward again.
• GitHub marks the newest release as "Latest" by default. v0.117.3 would be created after v0.119.0, so it would take that label.

#2029 already stopped the patch from moving the latest Docker tag.

Change

On this release branch only:

• Remove .github/workflows/web-sdk.yml, so a tag here does not publish to npm.
• Set skip_upload: true on the brew and scoop entries in .goreleaser.yml.
• Set release.make_latest: false in both GoReleaser configs.

A tag here still creates the GitHub release with its binaries, .deb and .rpm files, and pushes raystack/frontier:<tag>, <tag>-amd64 and <tag>-arm64 to Docker Hub. It also still pushes raystack/frontier:dev, which is unchanged.

main is unchanged, so releases from main keep publishing to npm, Homebrew and Scoop, and keep taking the "Latest" label.

Testing

• goreleaser check (v1.26.2, the version CI resolves for ~> v1) passes for .goreleaser-fast.yml. For .goreleaser.yml it reports only the brews.folder deprecation, which was already there before this change.
• The release workflow was not run, since that needs a tag.

[vercel]

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

Project	Deployment	Actions	Updated
frontier	Ready	Preview	Nov 3, 2026 11:41am 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
• File: .coderabbit.yaml
• Commit: 1bd1552
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 016ef49b-2075-4e48-bcaa-a618c33a0b11

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

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

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

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[coveralls]

Coverage Report for CI Build 41629487290

Warning

No base build found for commit fe89f89 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