Skip to content

Restrict tokio to 1.14 as a dev-dependency #1315

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

Merged

Conversation

TheBlueMatt
Copy link
Collaborator

This maintains our MSRV for simple cargo test runs, but doesn't
restrict users to any specific 1.X tokio version.

This maintains our MSRV for simple `cargo test` runs, but doesn't
restrict users to any specific 1.X tokio version.
@TheBlueMatt
Copy link
Collaborator Author

Note that this fixes the linting CI test.

@moneyball
Copy link
Contributor

fyi alternative view bitcoindevkit/bdk#547

@TheBlueMatt
Copy link
Collaborator Author

TheBlueMatt commented Feb 17, 2022

I think bumping MSRV beyond 1.41 is unacceptable, but I commented on the BDK issue.

@TheBlueMatt TheBlueMatt merged commit 84c3f51 into lightningdevkit:main Feb 17, 2022
notmandatory added a commit to bitcoindevkit/bdk that referenced this pull request Feb 18, 2022
b04bb59 Pin tokio version to ~1.14 (Steve Myers)

Pull request description:

  ### Description

  The `tokio` project recently changed their MSRV to `1.49.0`. This PR will pin the `tokio` dependency version to `~1.14` which is prior to their MSRV increase.

  ### Notes to the reviewers

  The LDK team took this approach for their `tokio` dev-dependency, see lightningdevkit/rust-lightning#1315.

  As long as `tokio` backports bug fixes  to`1.14.x` releases this should be safe. If we need any new features we can revisit this decision.

  ### Checklists

  #### All Submissions:

  * [x] I've signed all my commits
  * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md)
  * [x] I ran `cargo fmt` and `cargo clippy` before committing

  #### New Features:

  * [ ] I've updated `CHANGELOG.md`

ACKs for top commit:
  LLFourn:
    ACK b04bb59

Tree-SHA512: a44d61e0d644900837b5a99e0f2b9e5706cf9932f7430c3a2c8adbff37c82e4a6a545849fe031da748fcd8c8a70f5266d6974c5b6634b50af5eae148b9a26635
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.

4 participants