Skip to content

chore(main): release protoc-gen-elixir 0.1.1 - #64

Merged
yordis merged 1 commit into
mainfrom
release-please--branches--main--components--protoc-gen-elixir
Aug 2, 2026
Merged

chore(main): release protoc-gen-elixir 0.1.1#64
yordis merged 1 commit into
mainfrom
release-please--branches--main--components--protoc-gen-elixir

Conversation

@sht-bot

@sht-bot sht-bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

An automated release has been created for you.

0.1.1 (2026-08-02)

Bug Fixes

  • protoc-gen-elixir: Emit one file per service under one_file_per_module (#63) (6efd221)

This PR was generated with Release Please. See documentation.

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

cursor Bot commented Aug 2, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Manifest and changelog only; no generator or runtime code changes in this PR.

Overview
Release Please bumps protoc-gen-elixir from 0.1.0 to 0.1.1 in .github/.release-please-manifest.json and adds the matching 0.1.1 section to cmd/protoc-gen-elixir/CHANGELOG.md.

That release documents the bug fix from #63: with one_file_per_module=true, the generator now emits one .pb.ex file per service (and related gRPC modules), not only per message/enum module.

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

@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fce5d888-ce5c-4574-973d-6931a3d567fc

📥 Commits

Reviewing files that changed from the base of the PR and between bdf5adf and ded3291.

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

Walkthrough

The release manifest now targets 0.1.1. The changelog records the one-file-per-service bug fix for one_file_per_module.

Changes

Release metadata

Layer / File(s) Summary
Record version 0.1.1
.github/.release-please-manifest.json, cmd/protoc-gen-elixir/CHANGELOG.md
The release manifest changes from 0.1.0 to 0.1.1. The changelog records the corrected service-file emission behavior.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: yordis

Poem

A rabbit checks the release line,
“Zero-one-one” now reads just fine.
One service, one file, neatly spun,
The changelog marks the fix as done.
Hop, hop, ship! 🐇

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the release of protoc-gen-elixir version 0.1.1.
Description check ✅ Passed The description explains the protoc-gen-elixir 0.1.1 release and its bug fix.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--protoc-gen-elixir

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.

@yordis
yordis merged commit d80bf38 into main Aug 2, 2026
3 of 4 checks passed
@yordis
yordis deleted the release-please--branches--main--components--protoc-gen-elixir branch August 2, 2026 09:15
@sht-bot

sht-bot commented Aug 2, 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