Skip to content

chore: bump all package versions to 0.1.1 - #17

Merged
andrewklatzke merged 1 commit into
mainfrom
fix/bump-manifest-versions
Aug 6, 2026
Merged

chore: bump all package versions to 0.1.1#17
andrewklatzke merged 1 commit into
mainfrom
fix/bump-manifest-versions

Conversation

@andrewklatzke

@andrewklatzke andrewklatzke commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Manually bumps all 8 packages from 0.1.0 to 0.1.1 to skip past the burned 0.1.0 release (phantom immutable release blocking tag recreation).

Changes

  • .release-please-manifest.json: all packages 0.1.00.1.1
  • All 8 pyproject.toml version fields → 0.1.1
  • All 8 __init__.py __version__ fields → 0.1.1
  • uv.lock regenerated

Note

Low Risk
Version metadata and lockfile only; no application logic or dependency requirement changes beyond recorded versions.

Overview
Bumps all eight LaunchDarkly AI Python packages from 0.1.0 to 0.1.1 so releases can move past a burned 0.1.0 on the registry (immutable artifact blocking tag recreation).

Updates .release-please-manifest.json, each package’s pyproject.toml version, matching __version__ in package __init__.py, and uv.lock workspace package versions (from 0.0.0/0.1.0 to 0.1.1). No runtime or API code changes.

Reviewed by Cursor Bugbot for commit 4bff882. Bugbot is set up for automated code reviews on this repo. Configure here.

Manually set all 8 packages to 0.1.1 in the manifest, pyproject.toml
files, and __init__.py files to skip past the burned 0.1.0 release.

Co-authored-by: Cursor <cursoragent@cursor.com>
@andrewklatzke
andrewklatzke merged commit 5328b9d into main Aug 6, 2026
8 checks passed
@andrewklatzke
andrewklatzke deleted the fix/bump-manifest-versions branch August 6, 2026 18:01
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