publish: getsentry/[email protected]

[getsentry-release]

Requested by: @nikhars

Merge target: (default)

Quick links:

• View changes
• View check runs

Assign the accepted label to this issue to approve the release.
Leave a comment containing #retract under this issue to retract the release (original issuer only).

Targets

• github
• pypi
• sentry-pypi

Targets marked with a checkbox have already been executed. Administrators can manually tick a checkbox to force craft to skip it.

[github-actions]

Publishing: run#10798533035

[github-actions]

Failed to publish. (run logs)

Bad branch? You can delete with ease and start over.

[nikhars]

I have added the bypass rule for getsentry bot to allow directly committing to main. That is what failed the release based on the logs.

[debug] Merging release/0.0.3 into: main
Error:  To https://github.com/getsentry/sentry-infra-tools
!	refs/heads/main:refs/heads/main	[remote rejected] (push declined due to repository rule violations)
Done
Pushing to https://github.com/getsentry/sentry-infra-tools
POST git-receive-pack (402 bytes)
remote: error: GH013: Repository rule violations found for refs/heads/main.        
remote: Review all repository rules at http://github.com/getsentry/sentry-infra-tools/rules?ref=refs%2Fheads%2Fmain        
remote: 
remote: - 2 of 2 required status checks are expected.        
remote: 
error: failed to push some refs to 'https://github.com/getsentry/sentry-infra-tools'

[nikhars]

Based on this comment, seems like I should be able to start over. Going to do that since I also want to test the auto approve workflow I added