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

Reusable components of solo node update to be leveraged for SDK testing #528

Closed
jeromy-cannon opened this issue Aug 30, 2024 · 1 comment · Fixed by #735
Closed

Reusable components of solo node update to be leveraged for SDK testing #528

jeromy-cannon opened this issue Aug 30, 2024 · 1 comment · Fixed by #735
Assignees
@Ivo-Yankov
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released Requested by Stakeholder Requested by an individual or team that uses Solo

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Aug 30, 2024 •
edited
Loading

Please update and leverage this design doc to assist: Solo Reusability for DAB Test Cases (DRAFT)
relates to #522

depends on #499 to prevent merge conflicts
@jeromy-cannon jeromy-cannon mentioned this issue Aug 30, 2024
Open
@jeromy-cannon jeromy-cannon added the Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. label Aug 30, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Solo Aug 30, 2024
@jeromy-cannon jeromy-cannon moved this from 🆕 New to 📋 Backlog in Solo Aug 30, 2024
@jeromy-cannon jeromy-cannon added the P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. label Sep 3, 2024
@jeromy-cannon jeromy-cannon moved this from 📋 Backlog to 🔖 Ready in Solo Sep 3, 2024
@jeromy-cannon jeromy-cannon added the Requested by Stakeholder Requested by an individual or team that uses Solo label Sep 3, 2024
@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. and removed P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. labels Sep 10, 2024
@jeromy-cannon jeromy-cannon mentioned this issue Sep 10, 2024
Closed
@Ivo-Yankov Ivo-Yankov mentioned this issue Oct 24, 2024
Merged
@jeromy-cannon jeromy-cannon added P0 An issue impacting production environments or impacting multiple releases or multiple individuals. and removed P1 High priority issue. Required to be completed in the assigned milestone. labels Oct 24, 2024
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in Solo Oct 25, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.32.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

@Ivo-Yankov Ivo-Yankov

Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released Requested by Stakeholder Requested by an individual or team that uses Solo
Projects
Solo
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add separate commands for update hashgraph/solo
3 participants
@Ivo-Yankov @jeromy-cannon @swirlds-automation