-
Notifications
You must be signed in to change notification settings - Fork 55
build: bump rust-dashcore to dev head 78d10022 #3976
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
Open
Claudius-Maginificent
wants to merge
6
commits into
v4.1-dev
Choose a base branch
from
chore/bump-rust-dashcore-dev
base: v4.1-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+212
−93
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ef7cdf2
chore(deps): bump rust-dashcore to dev head 78d10022
lklimek 27d235f
fix(dpp): implement extended_public_key on shielded FixedKeySigner te…
lklimek 36e2fed
chore(deps): bump rust-dashcore to PR #833 (Zeroize for ExtendedPrivKey)
lklimek 3be6885
refactor(rs-sdk-ffi): wrap ExtendedPrivKey in Zeroizing, drop manual …
lklimek b175d50
refactor(rs-sdk-ffi): confine ExtendedPrivKey to resolve_and_derive v…
lklimek 5a2b2b5
test(rs-sdk-ffi): make extended_public_key metadata asserts load-bear…
lklimek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Blocking: Workspace pinned to unmerged rust-dashcore PR #833 branch head — repin before merging
All 8 rust-dashcore workspace dependencies are pinned to
f42498e0d04257e28b4e457c16629904a872ab61, which is the head of unmerged rust-dashcore PR #833 (theZeroize for ExtendedPrivKeychange this platform PR depends on). Merging this branch as-is would make platform's build depend on an integration PR commit rather than a protected upstream line — the branch could be rebased or force-pushed, invalidating the pin. The PR description already flags this as a pre-merge gate. Once rust-dashcore#833 lands ondev, repin all 8revvalues to the resultingdevhead (or a release tag) and refreshCargo.lockbefore this PR is merged.source: ['codex']
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still present at
b175d50.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct and already tracked — this is a deliberate interim state, not an oversight. The PR description's "Blocking relationship" and "Notes for reviewers" sections (updated with this push) call out the same gate explicitly: all 8 rev pins point at rust-dashcore PR #833's branch head because that's what supplies
Zeroize for ExtendedPrivKey, and this PR must not merge tov4.1-devuntil #833 lands on rust-dashcoredev(or a tag) and the pins are refreshed accordingly. Leaving this thread open as the pre-merge gate it is — will repin and refreshCargo.lockonce #833 merges upstream.🤖 Co-authored by Claudius the Magnificent AI Agent
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correction: this finding is still present at
5a2b2b50, not resolved. The current top-level review carries it forward as the single blocking issue:Cargo.tomlstill pins all 8 rust-dashcore workspace deps to unmerged PR #833 headf42498e0d04257e28b4e457c16629904a872ab61.The earlier auto-reconciliation text on this comment was wrong; the top-level review at this SHA is the canonical result.