Skip to content
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

Properly configure releases to NPM of the v5 + v6 versions #76

Closed
nicolethoen opened this issue Jul 31, 2024 · 1 comment
Closed

Properly configure releases to NPM of the v5 + v6 versions #76

nicolethoen opened this issue Jul 31, 2024 · 1 comment
Assignees
@nicolethoen

Comments

@nicolethoen
Copy link
Contributor

No description provided.

@nicolethoen nicolethoen self-assigned this Jul 31, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in PatternFly Issues Jul 31, 2024
@nicolethoen nicolethoen moved this from Needs triage to In Progress in PatternFly Issues Jul 31, 2024
@nicolethoen nicolethoen mentioned this issue Aug 1, 2024
Closed
@nicolethoen
Copy link
Contributor Author

it's done!

Anything merged into the main branch will release a 1.0.0-prerelease.x version - a manually triggered script will publish a 1.x version
anything merged into the v6 branch will release a 2.0.0-alpha.x version.

note - in order to trigger any sort of release upon merge, you must format your initial commit message using fix: or feat: semantic release formatting.

@github-project-automation github-project-automation bot moved this from In Progress to Done in PatternFly Issues Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nicolethoen nicolethoen

Labels
None yet
Projects
PatternFly Issues
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nicolethoen