chore: drop release-as pin so release-please bumps past 0.1.0

[diogocabral]

Problem

main ended up with two chore(main): release 0.1.0 commits (#3 and #5). The bootstrap "release-as": "0.1.0" in release-please-config.json forces every release PR back to 0.1.0, so the post-0.1.0 changes (the SSE/Accept fix #6, docs #4) never produced a new tag — merging the second release PR just tried to recreate the existing v0.1.0, which no-ops. Result: no v0.1.1, no GoReleaser, no updated Homebrew formula.

Fix

Remove the release-as pin. It's only meant to seed the first release version; with v0.1.0 already tagged and the manifest at 0.1.0, release-please now computes normal bumps from conventional commits — the pending fix: yields 0.1.1.

Manifest and CHANGELOG are left untouched (owned by the bot).

After merge

release-please re-runs → opens chore(main): release 0.1.1 → merging it tags v0.1.1 → GoReleaser updates the formula → brew upgrade gitvelocity ships the transport fix.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@diogocabral, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 11 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8f30bb41-b33b-419a-85d8-5db0a517dc04

📥 Commits

Reviewing files that changed from the base of the PR and between cc33345 and e53f2bb.

📒 Files selected for processing (1)

• release-please-config.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/drop-release-as-pin

---

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.}

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

6 × 0.1 = 0.6, floored to 1 (minimum)

Category	Score	Factors
🔭 Scope	1/20	Single config file, one line removed, no subsystem or logic impact
🏗️ Architecture	0/20	No architectural change
⚙️ Implementation	1/20	Trivial config key deletion, no logic involved
⚠️ Risk	2/20	Minor operational risk if 0.1.0 not yet released; easily reversible by re-adding the field
✅ Quality	2/15	No tests required; change is self-documenting and appropriate
🔒 Perf / Security	0/5	Not applicable for this change

Was this score accurate? 👍 Yes · 👎 No

_{Scored by GitVelocity · How are scores calculated?}

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

9 × 0.1 (Nano ESF) = 0.9, floored to 1

Category	Score	Factors
🔭 Scope	2/20	Single config file, one line removed, no subsystem or API impact
🏗️ Architecture	1/20	No architectural change; minor CI/CD release config adjustment
⚙️ Implementation	1/20	Trivial single-line deletion; requires release-please domain knowledge to understand intent
⚠️ Risk	3/20	Removes version pin allowing automated version computation; low risk, easily reversible by re-adding the field
✅ Quality	2/15	Config change with no applicable tests; change is self-documenting
🔒 Perf / Security	0/5	Not applicable for this config change

Was this score accurate? 👍 Yes · 👎 No

_{Scored by GitVelocity · How are scores calculated?}