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

chore(release): v0.40.2 #561

Merged
merged 2 commits into from
Jan 5, 2022
Merged

chore(release): v0.40.2 #561

merged 2 commits into from
Jan 5, 2022

Conversation

asyncapi-bot
Copy link
Contributor

Version bump in package.json for release v0.40.2

@coveralls
Copy link

Pull Request Test Coverage Report for Build 1655400235

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 93.234%
Totals Coverage Status
Change from base Build 1655380404: 0.0%
Covered Lines: 2316
Relevant Lines: 2365
💛 - Coveralls

@jonaslagoni
Copy link
Member

jonaslagoni commented Jan 4, 2022 •
edited
Loading

@derberg this is happening quite a lot where the CI is stuck, not sure if there is anything we can do on our end? You mentioned in another PR something about CI skip, but I can't find it 😅

Or is this purely GitHub actions problem 🤔?

@derberg derberg closed this Jan 5, 2022
@derberg
Copy link
Member

derberg commented Jan 5, 2022

6

@derberg derberg reopened this Jan 5, 2022
@derberg derberg closed this Jan 5, 2022
@derberg derberg reopened this Jan 5, 2022
@sonarcloud
Copy link

sonarcloud bot commented Jan 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

@derberg
Copy link
Member

derberg commented Jan 5, 2022

@jonaslagoni hanging happens, I trued to investigate why but it is super random and not something on our side. I think that for these bump PRs we could add skip ci to the message to ignore CI as we do not need them again when just bumoing version. Good candidate solution to optimize CI. Maybe there are other bot workflows we could optimize this way to. Please open issues in .gitihub and I'll have a look next week

@asyncapi-bot asyncapi-bot merged commit a897e07 into master Jan 5, 2022
@asyncapi-bot asyncapi-bot deleted the version-bump/v0.40.2 branch January 5, 2022 07:29
@asyncapi-bot
Copy link
Contributor Author

🎉 This PR is included in version 0.41.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@jonaslagoni jonaslagoni mentioned this pull request Jan 5, 2022
Closed
@asyncapi-bot
Copy link
Contributor Author

🎉 This PR is included in version 1.0.0-next.23 🎉

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
Reviewers

@jonaslagoni jonaslagoni jonaslagoni approved these changes

@github-actions github-actions[bot] github-actions approved these changes

Assignees
No one assigned
Labels
autoapproved released on @next released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@asyncapi-bot @coveralls @jonaslagoni @derberg