plugin bump

[akshaydeo]

Summary

Briefly explain the purpose of this PR and the problem it solves.

Changes

• What was changed and why
• Any notable design decisions or trade-offs

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Describe the steps to validate this change. Include commands and expected outcomes.

# Core/Transports
go version
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

If adding new configs or environment variables, document them here.

Screenshots/Recordings

If UI changes, add before/after screenshots or short clips.

Breaking changes

• Yes
• No

If yes, describe impact and migration instructions.

Related issues

Link related issues and discussions. Example: Closes #123

Security considerations

Note any security implications (auth, secrets, PII, sandboxing, etc.).

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 40 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 2da99aa0-c1f2-40b8-8204-7c7ecdf675d5

📥 Commits

Reviewing files that changed from the base of the PR and between f0668a3 and 2792c0a.

📒 Files selected for processing (1)

• plugins/otel/version

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-16-plugin_bump

---

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

[akshaydeo]

• plugin bump #4457 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[akshaydeo]

Merge activity

• Jun 16, 12:46 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 16, 12:47 PM UTC: @akshaydeo merged this pull request with Graphite.

[CLAassistant]

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

[greptile-apps]

Confidence Score: 4/5

The change is small, but publishing this backport as-is can redirect release metadata for the OTEL plugin away from the current 2.x track.

Only one version marker changed, and the release behavior for stable plugin versions was exercised against the local release logic.

plugins/otel/version

T-Rex Logs

What T-Rex did

• The base commit f0668a3 shows plugins/otel/version updated to 1.2.20.
• The head commit 2792c0a shows plugins/otel/version updated to 1.2.21.
• The version bump from 1.2.20 to 1.2.21 is observable and matches the PR claim.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "plugin bump" | Re-trigger Greptile}

[greptile-apps]

Avoid downgrading latest This stable 1.2.21 plugin release is older than the existing plugins/otel/v2.0.1 tag, but the plugin release script marks every non-prerelease plugin release as GitHub --latest. When this version is published, GitHub release metadata can point users and installers at the older 1.2.x backport instead of the current 2.x OTEL plugin. Please either bump the current track, or update the release flow so backport plugin releases are not marked latest.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!