Skip to content

chore(main): release 0.22.0 - #456

Open
roschaefer wants to merge 1 commit into
mainfrom
release-please--branches--main--components--git-splice
Open

roschaefer wants to merge 1 commit into
mainfrom
release-please--branches--main--components--git-splice

Conversation

@roschaefer

@roschaefer roschaefer commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

0.22.0 (2026-11-13)

Features

  • docs: prepare Netlify hosting with reusable GoatCounter splice (#482) (eae6958)
  • execution: run --exec hooks at pull and push checkpoints (#487) (4538e43)
  • pull: fetch the splices a pull or clone brings in (#455) (35420ed)
  • pull: pull --all goes down the tree, and a recursive pull's commit is its splice's pull (#461) (3f737e6)
  • push: a rebuild records each splice inside it at its own rebuild (#465) (613e790), closes #458
  • push: pause and continue at execution events (#479) (d0c5499)

Bug Fixes

  • pull: make a lost synced commit again from the branch's own history (#464) (32d93b3)
  • pull: pull --rebase --recursive rebases the monorepo's own commits once (#462) (7b827f7), closes #437

This PR was generated with Release Please. See documentation.

@coderabbitai

coderabbitai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The release version changes from 0.21.0 to 0.22.0. The changelog documents two pull features and a fix for recursive rebasing.

Changes: 0.22.0 release

Layer / File(s) Summary
Release metadata and notes
.release-please-manifest.json, Cargo.toml, CHANGELOG.md
The manifest and package version change to 0.22.0. The changelog records two pull features and a recursive rebase fix.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related issues

  • roschaefer/git-splice#351 — The change to which commit represents a recursive pull overlaps with the issue’s focus on pull commit messages; it does not add configurable message templates.
  • roschaefer/git-splice#360 — The release notes describe recursive traversal of nested splices, which overlaps with the issue’s focus on nested splice handling.
Merge Risk: Minimal · up to 1c9de

The release metadata and notes are consistent; no merge-blocking issue is identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title clearly identifies this as a release PR for version 0.22.0, which matches the version changes and release notes.
Linked Issues check Passed The only directly linked issue supplied is #437, which is closed. It provides historical context only. No active directly linked issue imposes coding requirements on this pull request.
Out of Scope Changes check Passed The summary shows only the 0.22.0 version updates in .release-please-manifest.json and Cargo.toml, plus the matching CHANGELOG.md release entry. These changes support the release PR and do not s…
Description check Passed The description is a Release Please release notes PR body for version 0.22.0 of git-splice. It lists features and bug fixes in pull, push, execution, and docs, which match the changeset: version bumps…
Full details: Out of Scope Changes check

Explanation

The summary shows only the 0.22.0 version updates in .release-please-manifest.json and Cargo.toml, plus the matching CHANGELOG.md release entry. These changes support the release PR and do not show unrelated changes.

Full details: Description check

Explanation

The description is a Release Please release notes PR body for version 0.22.0 of git-splice. It lists features and bug fixes in pull, push, execution, and docs, which match the changeset: version bumps in the manifest and Cargo.toml and the 0.22.0 CHANGELOG entry. The description is related to the changes, so the check passes.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • 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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6e650168-24e9-4667-a548-bd1e462596c3
Commits

Reviewing files that changed from the base of the PR and between 3c0a074 and 1c9dec6.

Files ignored due to path filters: 1

  • Cargo.lock is excluded by !**/*.lock
Files selected for processing: 3

  • .release-please-manifest.json
  • CHANGELOG.md
  • Cargo.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T11:54:52.506228Z d662111 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@roschaefer
roschaefer force-pushed the release-please--branches--main--components--git-splice branch 8 times, most recently from 4f34ed4 to eb04a41 Compare November 12, 2026 19:07
@roschaefer
roschaefer force-pushed the release-please--branches--main--components--git-splice branch from eb04a41 to 3659ae7 Compare November 13, 2026 19:40

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

push --all sends stale records of nested splices to the upstreams above pull --rebase of nested splices replays the pulls of the splices above

1 participant