Skip to content

Conversation

ShGKme
Copy link
Contributor

@ShGKme ShGKme commented Feb 10, 2025

npm run post-release:milestones

Update milestones after the release:
	1. Renames the current milestone to the release milestone (Next Release -> v1.2.3)
	2. Creates the next milestone as a replacement for the current (Next Release)
	3. Moves all open issues and PRs from the current=release milestone to the new milestone (v1.2.3 -> Next Release)
	4. Closes the current=release milestone
USAGE:
	npm run post-release:milestones
	npm run post-release:milestones -- -y --current="🪴 Next Release" --release="v1.2.3" --next="🌵 Next Release"
ARGS:
	--help - show help
	-y - skip confirmation
	--current - Optionally the current milestone to rename. Default is "🪴 Next Release".
	--release - Optionally the release version to rename the source milestone to. Default is the v + package.json version.
	--next - Optionally the new milestone to create. Default is --source, which is "🪴 Next Release".

Full flow

image

When almost done already

image

@ShGKme ShGKme added 3. to review technical debt Maintenance and refactoring labels Feb 10, 2025
@ShGKme ShGKme self-assigned this Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review technical debt Maintenance and refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant