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

CQ: Fix issue with main branch coverage reports not including E2E results #112

Closed
Tracked by #50
nathanklick opened this issue Feb 28, 2024 · 1 comment · Fixed by #113
Closed
Tracked by #50

CQ: Fix issue with main branch coverage reports not including E2E results #112

nathanklick opened this issue Feb 28, 2024 · 1 comment · Fixed by #113
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs released

Comments

@nathanklick
Copy link
Member

No description provided.

@nathanklick nathanklick mentioned this issue Feb 28, 2024
Open
@nathanklick nathanklick added the Bug A error that causes the feature to behave differently than what was expected based on design docs label Feb 28, 2024
@nathanklick nathanklick mentioned this issue Feb 28, 2024
Merged
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.22.0 🎉

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
Assignees
No one assigned
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs released
Projects
Solo
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(ci): ensure e2e coverage reports are analyzed for main branch commits hashgraph/solo
2 participants
@nathanklick @swirlds-automation