Skip to content

chore: sync main into development after v0.11.1; open 0.11.2rc1 - #1067

Merged
cemililik merged 3 commits into
developmentfrom
chore/sync-main-after-v0.11.1
Oct 23, 2026
Merged

cemililik merged 3 commits into
developmentfrom
chore/sync-main-after-v0.11.1

Conversation

@cemililik

@cemililik cemililik commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Post-release sync for v0.11.1. It brings main's release merge commit back into development, as docs/standards/release.md requires after every release, and opens the next development cycle. Merge with "Create a merge commit", so the sync keeps its second parent.

Related issues

None.

Changes

  • a4e1d1a. Merges main (2636b5c, the Release v0.11.1 — Fail Closed (Windows fix before publishing) #1066 merge commit that v0.11.1 points to) into development. No file changes, so main carries no commit that development lacks.
  • 7527a78. Bumps pyproject.toml from 0.11.1 to 0.11.2rc1, the next development cycle (precedent: 6335dc2 after v0.11.0). CHANGELOG.md already has the empty [Unreleased] section. The rc marker is not a version promise: the next cycle's tag is still derived at the cut from the bump table.

Type

  • CI / infrastructure (release)

Testing

  • check_notebook_pins, check_release_record_sync, check_deprecation_targets, check_site_claims and update_site_version --check all pass with the rc version. The notebooks and the site keep 0.11.1, the latest release.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the project version to 0.11.2rc1, marking a release candidate for the next version.
    • No user-facing feature or behavior changes are included in this update.

cemililik and others added 3 commits October 23, 2026 22:33
Release v0.11.1 — Fail Closed (Windows fix before publishing)
…1066)

Bring back the merge commit of the v0.11.1 release pull request so main carries no commit development lacks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coldtea-pr-lens

Copy link
Copy Markdown

Note

The title starts with chore:, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

github.comment.notice: false in .github/pr-lens.yml turns this note off

@sourcery-ai

sourcery-ai Bot commented Oct 23, 2026

Copy link
Copy Markdown

Sorry @cemililik, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 21 hours and 7 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

@coderabbitai

coderabbitai Bot commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: d570e41f-fccf-4e46-bb4b-5ef947e53b11
📥 Commits

Reviewing files that changed from the base of the PR and between 8c483eb and 7527a78.

📒 Files selected for processing: 1
  • pyproject.toml
+-----------------------------------+
| Faking self-awareness since 2023. |
+-----------------------------------+
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ 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

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

@cemililik
cemililik merged commit 83e62f6 into development Oct 23, 2026
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant