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

fix: hot for removing breaking change in wallet, new release for nexnet v1.0.0-rc.8 #6305

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

SWvheerden
Copy link
Collaborator

Description

Removed breaking change of wallet db type
Release new nextnet version

Motivation and Context

Release v1.0.0-rc.7 accidentally included an unmarked breaking change. This change is for future ledger support in with saving the wallet type as software or ledger in the wallet db. This is a breaking change. This forces a wallet to be software as ledger is currently in dev and not yet functioning.

How Has This Been Tested?

Manual

Copy link
Contributor

@hansieodendaal hansieodendaal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@ghpbot-tari-project ghpbot-tari-project added the P-acks_required Process - Requires more ACKs or utACKs label Apr 23, 2024
Copy link

Test Results (CI)

    3 files    120 suites   36m 22s ⏱️
1 277 tests 1 277 ✅ 0 💤 0 ❌
3 823 runs  3 823 ✅ 0 💤 0 ❌

Results for commit 129ad9c.

Copy link

Test Results (Integration tests)

 2 files  11 suites   15m 26s ⏱️
33 tests 32 ✅ 0 💤 1 ❌
34 runs  33 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit 129ad9c.

@SWvheerden SWvheerden merged commit 07131ad into tari-project:nextnet Apr 23, 2024
14 of 16 checks passed
@SWvheerden SWvheerden deleted the sw_hotfix branch April 29, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-acks_required Process - Requires more ACKs or utACKs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants