#526 ci: sync the release-pipeline fixes back from main

[Anonymous]

Originally created by: adityaharishch

Brings pre-main level with the release-pipeline fixes that landed directly on main as [#523] and [#525].

Why they bypassed pre-main

release-prepare.yml and .releaserc.json are read from the branch the workflow runs on. Routing the fixes through pre-main would have meant waiting for a pre-main → main release merge - which is precisely what was broken. So they went to main directly, correctly for the emergency, leaving pre-main three files behind.

Why sync now

Not a revert risk. Git's three-way merge would keep main's side on the next release merge, since only main touched these files.

It is a conflict risk. pre-main is where all normal work happens, and there is a lot of CI work in flight. The moment someone edits these files here, the next release merge conflicts on them - and a careless "take theirs" silently undoes fixes that were expensive to find.

Carried over

• release-prepare.yml - fails loudly when a push to main tags nothing, with a step summary naming the squash-merge cause; exempts semantic-release's own chore(release) bump commit so a successful release does not end in a red X
• .releaserc.json - drops the skip-CI marker from the bump commit, so the release tag pointing at that commit actually triggers release-build (this is what left v1.74.1 tagged-but-unbuilt)
• ci.yml - the comment now describes the marker instead of quoting it verbatim

⚠️ Only the comment was taken from ci.yml, not the file

Copying main's ci.yml wholesale would have reverted the screenpipe-fork pin:

-          expected="064c44ccd8c50716f21eec1663e1350e848ca5f5"   ← pre-main (current)
+          expected="825b038d845d7dcc8c1387b2707899b352417233"   ← main (older)

pre-main advanced that pin in fix/bump-screenpipe-fork-sck-universal-disable, which has not reached main yet. Only the four comment lines were applied; the pin is untouched, and the pre-push run resolved 064c44cc from the fork as expected.

The version bumps and CHANGELOG entries for 1.74.1 / 1.74.2 are deliberately not carried over - that is main-only bookkeeping, and pre-main stamps its version from the tag at build time rather than reading Cargo.toml.

No behaviour change on pre-main

The guard's new branch is gated on GITHUB_REF_NAME = main, and the staging channel uses .releaserc.staging.json, which has no @semantic-release/git plugin. Staging releases are unaffected either way.

Verification

.releaserc.json parses as JSON, both workflows parse as YAML, screenpipe pin confirmed still 064c44cc, full pre-push suite green.

[Anonymous]

Originally posted by: coderabbitai[bot]

[!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

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7ce45343-d398-41ee-8108-6edf389461fb

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

- [ ] Create PR with unit tests - [ ] Commit unit tests in branch `ci/sync-release-fixes-to-pre-main`

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

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

[Anonymous]

Ticket changed by: adityaharishch

• status: open --> closed