chore(main): release protoc-gen-connect-go-servicestruct 0.1.1

[sht-bot]

An automated release has been created for you.

0.1.1 (2025-09-18)

Bug Fixes

• Using the go import path (#9) (cf849b6)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Walkthrough

Bumps .github/.release-please-manifest.json entry for cmd/protoc-gen-connect-go-servicestruct from 0.1.0 to 0.1.1 and adds a 0.1.1 section to cmd/protoc-gen-connect-go-servicestruct/CHANGELOG.md documenting a bug fix.

Changes

Cohort / File(s)	Summary
Release tooling .github/.release-please-manifest.json	Update manifest value for cmd/protoc-gen-connect-go-servicestruct from 0.1.0 to 0.1.1.
Changelog cmd/protoc-gen-connect-go-servicestruct/CHANGELOG.md	Add 0.1.1 entry (2025-09-18) noting bug fix: using the Go import path, with links to issue #9 and commit cf849b6.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(main): release protoc-gen-connect-go-servicestruct 0.1.0 #8 — Previously added the same manifest entry at version 0.1.0; this PR increments it to 0.1.1.

Suggested labels

autorelease: tagged

Poem

I twitch my whiskers at 0.1.1, hooray!
A hop from zero-one-oh to one-one today.
Changelog crumbs lead down the import trail,
Bug burrow patched—no more stale.
Thump-thump, release drums—ship away! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "chore(main): release protoc-gen-connect-go-servicestruct 0.1.1" succinctly and accurately summarizes the primary change (a release bump to v0.1.1) and matches the manifest and changelog edits in the changeset. It is concise, single-sentence, and uses a conventional commit-style prefix, so it meets the criteria for a clear PR title.
Description Check	✅ Passed	The PR description is an automated Release Please release note that documents version 0.1.1 and its bug fix, and it directly corresponds to the manifest and CHANGELOG changes present in this PR, so it is related to the changeset. The level of detail is adequate for this lenient check.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-please--branches--main--components--protoc-gen-connect-go-servicestruct

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sht-bot]

🤖 Created releases:

• protoc-gen-connect-go-servicestruct@v0.1.1

🌻

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

cmd/protoc-gen-connect-go-servicestruct/CHANGELOG.md (1)

3-9: Changelog polish: link/style consistency + capitalization nit

• Header style differs from 0.1.0 (linked vs plain). If you want consistent formatting across versions, either link both or keep both plain.
• Capitalize “Go” in the bullet.

-## 0.1.0 (2025-09-18)
+## [0.1.0](https://github.com/TrogonStack/protoc-gen/compare/protoc-gen-connect-go-servicestruct@v0.0.0...protoc-gen-connect-go-servicestruct@v0.1.0) (2025-09-18)

-* Using the go import path ([#9](https://github.com/TrogonStack/protoc-gen/issues/9)) ([cf849b6](https://github.com/TrogonStack/protoc-gen/commit/cf849b60675d71e35ee5fb0df9c7a2ba424c7877))
+* Using the Go import path ([#9](https://github.com/TrogonStack/protoc-gen/issues/9)) ([cf849b6](https://github.com/TrogonStack/protoc-gen/commit/cf849b60675d71e35ee5fb0df9c7a2ba424c7877))

If you prefer the current mixed style, ignore the header change. Please also confirm the compare link resolves as expected.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf849b6 and 468ebc8.

📒 Files selected for processing (2)

• .github/.release-please-manifest.json (1 hunks)
• cmd/protoc-gen-connect-go-servicestruct/CHANGELOG.md (1 hunks)

🔇 Additional comments (1)

.github/.release-please-manifest.json (1)

2-2: Version bump matches changelog 0.1.1

Looks good. Confirm the release PR will create the tag and GitHub Release for this component.

You can verify planned tagging with Release Please’s PR checks or by inspecting the generated release notes after merge.