Skip to content

Update nightly toolchain to nightly-2026-03-14#73

Closed
nyonson wants to merge 1 commit intomasterfrom
automated/update-nightly
Closed

Update nightly toolchain to nightly-2026-03-14#73
nyonson wants to merge 1 commit intomasterfrom
automated/update-nightly

Conversation

@nyonson
Copy link
Collaborator

@nyonson nyonson commented Mar 1, 2026

Automated changes by create-pull-request GitHub action

@nyonson nyonson changed the title Update nightly toolchain to nightly-2026-02-28 Update nightly toolchain to nightly-2026-03-07 Mar 8, 2026
@nyonson nyonson force-pushed the automated/update-nightly branch from c5844d7 to f06f9da Compare March 8, 2026 01:56
@nyonson nyonson force-pushed the automated/update-nightly branch from f06f9da to 494797b Compare March 15, 2026 02:08
@nyonson nyonson changed the title Update nightly toolchain to nightly-2026-03-07 Update nightly toolchain to nightly-2026-03-14 Mar 15, 2026
@apoelstra
Copy link
Member

What's up with CI here? Should I be running my local CI on stuff here? (Note that it will be way faster than on rust-bitcoin because it's just one crate without a huge feature set. Probably it'd be feasible for other people to run it if they were so inclined.)

@nyonson
Copy link
Collaborator Author

nyonson commented Mar 17, 2026

What's up with CI here?

There wasn't much here before so I have been using it as a test bed for cargo-rbmt. Which appears to have burst into flames...but the fix (to my bug) is looking good: #80

Should I be running my local CI on stuff here?

As we switch over to this being the PSBT home we probably want the highest bar, so yes? I admit I'd love for cargo-rbmt to match that, but I am not sure if it's there yet.

@nyonson
Copy link
Collaborator Author

nyonson commented Mar 17, 2026

Gonna close this out and just wait for the next week to pick up the new version.

@nyonson nyonson closed this Mar 17, 2026
@tcharding
Copy link
Member

Should I be running my local CI on stuff here?

I'd personally like to crank like f*** in this repo with minimal roundtrip delays between devs. At least until we have made a bunch of progress. Can we just use GitHub actions as CI and one-ack merge policy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants