Skip to content

chore(main): release 0.15.0#55

Merged
yordis merged 1 commit into
mainfrom
release-please--branches--main
May 28, 2026
Merged

chore(main): release 0.15.0#55
yordis merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@sht-bot

@sht-bot sht-bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.15.0 (2026-05-28)

Features

  • content: Introduce typed content envelope (#54) (9b413b5)

This PR was generated with Release Please. See documentation.

Signed-off-by: Straw Hat Team Bot <61149376+sht-bot@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented May 28, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c42aa137-9c05-45bd-a929-7d360d1c36c3

📥 Commits

Reviewing files that changed from the base of the PR and between 9b413b5 and 269a31e.

📒 Files selected for processing (2)
  • .github/release-please-manifest.json
  • CHANGELOG.md

Walkthrough

This PR bumps the project version from 0.14.0 to 0.15.0 by updating the Release-Please version manifest and adding a corresponding changelog entry documenting the typed content envelope feature introduced in this release.

Changes

Release Version Update

Layer / File(s) Summary
Release manifest and changelog update
.github/release-please-manifest.json, CHANGELOG.md
Version is incremented to 0.15.0 in the release manifest, and a new changelog section documents the typed content envelope feature introduced in this release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • TrogonStack/trogon-proto#49: Both PRs only bump the . entry in .github/release-please-manifest.json and add corresponding version sections to CHANGELOG.md, with no code/function-level changes.
  • TrogonStack/trogon-proto#38: Both PRs only bump .github/release-please-manifest.json for the "." key and add corresponding CHANGELOG.md release sections (different version numbers).
  • TrogonStack/trogon-proto#51: Both PRs update the same Release-Please version mapping and add corresponding new CHANGELOG.md release sections for successive versions.

Suggested labels

autorelease: tagged

Suggested reviewers

  • yordis

Poem

🐰 A version bumped with gentle care,
From 0.14 to 0.15 fair,
The typed envelope takes its place,
In changelog's warm and welcoming space!
Release-please hops with glee,
This small PR, yet vital it be. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(main): release 0.15.0' directly and clearly summarizes the main change: releasing version 0.15.0.
Description check ✅ Passed The description is related to the changeset, documenting the release notes with feature details and version bump information.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@yordis yordis merged commit 988e763 into main May 28, 2026
2 of 3 checks passed
@yordis yordis deleted the release-please--branches--main branch May 28, 2026 00:39
@sht-bot

sht-bot commented May 28, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

2 participants