Skip to content

fix: Clarify how to retract a release - #5533

Merged
asottile-sentry merged 4 commits into
getsentry:mainfrom
philipphofmann:fix/clarify-retract
Jun 6, 2025
Merged

fix: Clarify how to retract a release#5533
asottile-sentry merged 4 commits into
getsentry:mainfrom
philipphofmann:fix/clarify-retract

Conversation

@philipphofmann

Copy link
Copy Markdown
Contributor

Clarify that you must leave a comment only containing retract and nothing else to retract a release.

Clarify that you must leave a comment only containing retract and
nothing else to retract a release.
@philipphofmann
philipphofmann requested a review from a team as a code owner May 9, 2025 07:22
@philipphofmann

Copy link
Copy Markdown
Contributor Author

I think we must merge getsentry/action-prepare-release#40 first. I need some help to merge and fix this, because I have no clue what the workflow is.

@asottile-sentry

Copy link
Copy Markdown
Contributor

I think getsentry/action-prepare-release#40 needs to be reverted and reapplied with the actual way

@philipphofmann

Copy link
Copy Markdown
Contributor Author

I updated this PR to match getsentry/action-prepare-release#41. We don't need to revert it.

@philipphofmann

Copy link
Copy Markdown
Contributor Author

@asottile-sentry asottile-sentry left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asottile-sentry
asottile-sentry merged commit 2821352 into getsentry:main Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants