Repository navigation
release: v2.14.1 - #943
Merged
Merged
release: v2.14.1#943
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
|
Warning Review limit reached
Your plan currently allows 1 review/hour. Refill in 18 minutes and 31 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
github-actions
Bot
added
dependencies
|
Failed to generate code suggestions for PR |
|
Size Change: +306 B (+0.07%) Total Size: 424 kB 📦 View Changed
ℹ️ View Unchanged
|
|
LucasSantana-Dev
added a commit
that referenced
this pull request
May 23, 2026
…946) ## Root cause The `ff-active-release` job fires on every push to `main`. After a squash-merge release (e.g. `release: v2.14.1 (#943)`), the job found `release/v2.14.0` as the latest `release/v*` branch and tried to fast-forward it to `main`. Because Lucky uses squash merges, individual commits on `release/v2.14.0` are not in `main`'s history — only the squash commit (`524655de`) is. So `git merge-base --is-ancestor release/v2.14.0 main` returns false and the job exits 1. ``` Warning: main is NOT an ancestor of release/v2.14.0 — divergence detected. Manual sync required. Error: Process completed with exit code 1. ``` ## Fix Before attempting a fast-forward, check if the branch's semver tag already exists on the remote (`git ls-remote --tags`). If the tag exists, the release has shipped — the branch should be archived, not synced: 1. Push the branch pointer to `archive/release-vX.Y.Z` 2. Delete the stale `release/vX.Y.Z` branch 3. Exit 0 Future workflow runs find no `release/v*` branch and skip cleanly. The normal FF path is unchanged for in-progress release branches (where the version tag does not yet exist).
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Patch release v2.14.1.
Changes since v2.14.0
Fixed
CHANGELOG.mdin the frontend build stage context — resolves broken production frontend image since v2.13.0 (fix(docker): copy CHANGELOG.md into frontend build context #937)Internal
quality-gatesjob into four parallel test jobs; absorbsonarcloud.ymlintoci.yml— tests run once with coverage, SonarCloud downloads artifacts. PR wall time ~8–10 min vs ~13–15 min (ci: parallel test jobs + eliminate duplicate test runs #942).husky/post-mergehook to auto-prune local branches whose remote has been deleted (chore(git): add post-merge hook to auto-prune [gone] local branches #941)