Skip to content

chore(main): release 0.15.0 - #396

Open
kong-volcano-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--volcano-sdk
Open

kong-volcano-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--volcano-sdk

Conversation

@kong-volcano-app

@kong-volcano-app kong-volcano-app Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.15.0 (2026-10-16)

Features

  • durable: wait for, publish, send, and subscribe to durable messages (#391) (dda9a6a)

Bug Fixes

  • sandboxes: sync runtime billing API contract (#392) (8a91a03)

This PR was generated with Release Please. See documentation.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@kong-volcano-app kong-volcano-app Bot changed the title chore(main): release 0.14.1 chore(main): release 0.15.0 Oct 16, 2026
@kong-volcano-app
kong-volcano-app Bot force-pushed the release-please--branches--main--components--volcano-sdk branch from 31bb271 to e4300a3 Compare October 16, 2026 19:13
@github-actions

Copy link
Copy Markdown

AI review: no P0-P2 findings

Reviewed e4300a3. Run log

This is the Release Please PR for 0.15.0. It bumps the version from 0.14.0 to 0.15.0 in .release-please-manifest.json, pyproject.toml, and uv.lock, and adds a CHANGELOG entry for the durable-messages feature (#391) and the sandboxes billing fix (#392). The three version strings match, and no other file still says 0.14.0. The changelog lists the user-facing commits made since v0.14.0, and a minor bump fits a pre-1.0 release that adds a feature. Risk is low.

Not checked: The AI review read the diff, the code, and the PR's text; it ran no tests or builds and read nothing outside this repository.

  • Whether the release workflow that runs after merge publishes 0.15.0 to the package index, and tags it correctly.

Human review: not needed

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.

1 participant