Skip to content

release: 0.12.0 - #52

Closed
stainless-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--changes--next
Closed

release: 0.12.0#52
stainless-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.12.0 (2026-08-21)

Full Changelog: v0.11.2...v0.12.0

Features

Bug Fixes

  • audit locked Python dependencies (#22) (b3427e6)
  • load search coverage responses (683edd6)
  • refresh release lockfile (e0b12a2)
  • synchronize Python release lockfile (c643e63)

Chores

  • add Context7 refresh workflow (618c494)
  • add FUNDING.yml pointing to xquik.com (6f6484f)
  • add per-file license evidence (9c46658)
  • deps: bump github/codeql-action/upload-sarif from 4.37.1 to 4.37.6 (#35) (d5909c0)
  • deps: bump google/clusterfuzzlite/actions/build_fuzzers (#26) (579f53a)
  • deps: bump google/clusterfuzzlite/actions/run_fuzzers (#25) (846c5ff)
  • deps: bump ossf/scorecard-action from 2.4.3 to 2.4.4 (#37) (e985625)
  • deps: bump pypa/gh-action-pypi-publish from 1.14.0 to 1.14.1 (#27) (f8d425d)
  • deps: bump pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2 (#42) (0f33a5e)
  • prepare 0.8.0 (#31) (5bee02f)
  • prepare v0.4.3 (93f496e)
  • refresh all Python dependencies (#47) (ab7ac3a)
  • sync lockfile version for 0.10.1 (47451b9)

Documentation

  • add Contributor Covenant 2.1 Code of Conduct (#2192) (06635a2)
  • add DeepWiki badge (34ca646)
  • clarify repository discovery (32c6e61)
  • map common X data tasks (#16) (9c5827e)
  • readme: add search-first SDK landing page (509d7a2)
  • refine public Python SDK text (#49) (811c7c2)
  • tighten Python SDK copy (1a038e9)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 2702e82 to 5aabb3b Compare August 21, 2026 02:54
@stainless-app stainless-app Bot changed the title release: 0.11.2 release: 0.12.0 Aug 21, 2026
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 5aabb3b to bf0b24e Compare August 21, 2026 02:55
@kriptoburak

Copy link
Copy Markdown
Member

Closing after a full audit. The base is already published as v0.11.2, and this range contains only the release commit with no runtime delta. The proposed changelog repeats released work, and uv.lock still records package version 0.11.2, so frozen CI fails. A local lock correction passed lint, types, 100% test suites, coverage gates, audit, reproducible builds, and package checks, but it cannot make an empty and misleading v0.12.0 release valid. Repair release tracking and recreate the PR after genuine unreleased changes exist.

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.

1 participant