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.

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

ci(release): use new branch naming strategy #546

Merged
merged 1 commit into from
May 10, 2022

Conversation

smoya
Copy link
Member

@smoya smoya commented May 5, 2022

Relates to asyncapi/spec#734 (comment)

This PR changes the package.json file to reflect the changes on the branch naming strategy for releasing; using next-spec and next-major-spec branches, plus next-major in this particular case.

@sonarcloud
Copy link

sonarcloud bot commented May 5, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@smoya
Copy link
Member Author

smoya commented May 9, 2022

Weird no reviewers were assigned. Pinging them here: @magicmatatjahu @jonaslagoni @derberg @fmvilas

EDIT: I promise GH UI showed me reviewers assigned to be zero, plus didn't show up this:
2022-05-09 at 08 58 32

@magicmatatjahu
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit 6d5563e into asyncapi:master May 10, 2022
@derberg
Copy link
Member

derberg commented May 10, 2022

next-spec created

@smoya smoya deleted the ci/branches branch May 10, 2022 12:41
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 1.15.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 2.0.0-next-major.18 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

4 participants