Skip to content

chore: remove prerelease setting in release-please config #5363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
May 14, 2025
Merged

chore: remove prerelease setting in release-please config #5363

merged 2 commits into from
May 14, 2025

Conversation

JoshuaKGoldberg
Copy link
Member

PR Checklist

Overview

Removes the prerelease and versioning properties as suggested in #5345 (comment) & #5345 (comment).

@JoshuaKGoldberg JoshuaKGoldberg mentioned this pull request May 12, 2025
Open
5 tasks
@JoshuaKGoldberg JoshuaKGoldberg requested a review from a team May 12, 2025 15:53
@voxpelli
Copy link
Member

Did we remove --tag=next from the npm command as well? Else we should do that here as well

voxpelli
voxpelli approved these changes May 12, 2025
View reviewed changes
Copy link
Member

@voxpelli voxpelli left a comment

Choose a reason for hiding this comment

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

Lgtm

@JoshuaKGoldberg JoshuaKGoldberg merged commit 8878f22 into mochajs:main May 14, 2025
75 checks passed
@github-actions github-actions bot mentioned this pull request May 14, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@voxpelli voxpelli voxpelli approved these changes

@mark-wiemer mark-wiemer mark-wiemer approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

🛠 Repo: npm releases not marked as latest
3 participants
@JoshuaKGoldberg @voxpelli @mark-wiemer