chore!: update feature-dan2 #1184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test Results (CI)578 tests +1 578 ✅ +1 3h 20m 8s ⏱️ + 13m 44s Results for commit c6f3613. ± Comparison against base commit 1d4e316. This pull request removes 2 and adds 3 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
* development: feat(consensus)!: suspend nodes that fail to participate (tari-project#1181) chore(deps-dev): bump vite from 4.5.3 to 4.5.5 in /applications/tari_swarm_daemon/webui (tari-project#1177) chore(deps-dev): bump vite from 4.5.3 to 4.5.5 in /applications/tari_dan_wallet_web_ui (tari-project#1178)
* development: feat(swarm): register templates on startup automatically if not already registered (tari-project#1185)
sdbondi
force-pushed
the
update-feature-dan2
branch
from
31d4b05 to
9f994d0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
chore!: update feature-dan2
chore: update to wasmer 4
chore: update to rust stable
Motivation and Context
Requires PR tari-project/tari#6644
Allow us to use rust > 1.77 by updating wasmer. We can remove various locks in the Runtime after this change but this is left for another PR.
How Has This Been Tested?
Manually
What process can a PR reviewer use to test or verify this change?
Breaking Changes