Skip to content

Revert "Prepare Release using 'release-plan'"#693

Merged
mansona merged 1 commit intomainfrom
reset-release
Feb 26, 2026
Merged

Revert "Prepare Release using 'release-plan'"#693
mansona merged 1 commit intomainfrom
reset-release

Conversation

@mansona
Copy link
Copy Markdown
Member

@mansona mansona commented Feb 26, 2026

The release from #678 failed so this resets the version and the changelog to make sure we release everything properly

We need to merge #692 before we attempt to release again 👍

@mansona mansona requested a review from a team February 26, 2026 18:03
Copy link
Copy Markdown
Contributor

@void-mAlex void-mAlex left a comment

Choose a reason for hiding this comment

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

don't we need to revert the .release-plan.json as well?

@mansona
Copy link
Copy Markdown
Member Author

mansona commented Feb 26, 2026

don't we need to revert the .release-plan.json as well?

No, the only thing that should ever touch the .release-plan.json file is the prepare release PR. This is because we try to publish main on commits where the .release-plan.json has changed, and reverting it will change it.

We don't need to worry about reverting it anyway because it's an ephemeral file and it will be re-created exactly as it needs to be once we open a new plan release PR 👍

@mansona mansona merged commit 752a0c8 into main Feb 26, 2026
141 of 145 checks passed
@mansona mansona deleted the reset-release branch February 26, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants