Skip to content

Revert "chore: release main" - #13

Merged
andrewklatzke merged 1 commit into
mainfrom
revert-11-release-please--branches--main
Jul 31, 2026
Merged

Revert "chore: release main"#13
andrewklatzke merged 1 commit into
mainfrom
revert-11-release-please--branches--main

Conversation

@andrewklatzke

Copy link
Copy Markdown
Contributor

Reverts #11

@andrewklatzke
andrewklatzke merged commit 8b8d943 into main Jul 31, 2026
7 checks passed
@andrewklatzke
andrewklatzke deleted the revert-11-release-please--branches--main branch July 31, 2026 23:08
andrewklatzke added a commit that referenced this pull request Aug 5, 2026
Reverts #13

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and changelog-only changes with no logic modifications; main
risk is release tagging/PyPI publish coordination if this merge triggers
the release workflow.
> 
> **Overview**
> Re-applies the **release-please** `0.1.0` release across the monorepo
(after reverting a prior revert of `chore: release main`).
> 
> Every listed workspace moves from **`0.0.0` → `0.1.0`**:
`.release-please-manifest.json`, each package’s `pyproject.toml`
`version`, `__version__` in package `__init__.py`, and a new **0.1.0
(2026-07-31)** section in each `CHANGELOG.md` documenting the initial
SDK feature commits. No runtime or API code changes beyond the version
strings.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
4e12892. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
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.

2 participants