egress: bump version to v2.3.2 for SigNoz cardinality fix#366
Merged
Conversation
The auto-bump in release-egress.yml failed on the #365 merge because the GITHUB_TOKEN cannot push directly to main (branch protection requires PRs). Bumping via a PR lands in the "manual bump detected" branch of the workflow, which skips the auto-push and proceeds to build+release. Once this merges, the workflow will publish v2.3.2 with the otelhttp /ws cardinality fix from #365. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository-wide version constant to v2.3.2 so the egress release workflow detects a manual bump (avoiding protected-branch direct pushes) and can publish the v2.3.2 release that includes the SigNoz cardinality fix from #365.
Changes:
- Bump
common.Versionfromv2.3.1tov2.3.2.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The auto-bump step in release-egress.yml failed on the #365 merge — the workflow's GITHUB_TOKEN can't push directly to `main` (branch protection requires PRs):
```
auto patch-bump: v2.3.1 -> v2.3.2
[main 5e5a271] chore: bump egress version to v2.3.2 [skip ci]
remote: error: GH006: Protected branch update failed for refs/heads/main.
remote: - Changes must be made through a pull request.
```
Fix
The workflow already handles manual bumps via PR (takes the "manual bump detected" branch, skips auto-commit/push). Bumping via this PR is the path of least resistance.
When merged: the next workflow run reads `current=v2.3.2 != last_tag=v2.3.1`, picks the manual-bump branch, skips the protected-branch fight, builds linux/amd64+arm64, publishes the v2.3.2 GitHub Release.
Then the running egress can be updated to pick up the otelhttp metric suppression from #365 and the SigNoz cardinality spike subsides.
Permanent fix (separate PR)
Branch protection will keep biting future releases. Options: allowlist github-actions[bot] for direct push, switch the workflow to open a PR instead, or use a GitHub App with bypass permission.
🤖 Generated with Claude Code