build(deps): bump bitvec from 1.0.1 to 1.1.1

[dependabot]

Bumps bitvec from 1.0.1 to 1.1.1.

Changelog

Sourced from bitvec's changelog.

Changelog

All notable changes will be documented in this file.

This document is written according to the [Keep a Changelog][kac] style.

1. Version 1
   1. 1.1.0
   2. 1.0.1
   3. 1.0.0
2. Version 0 (https://github.com/ferrilab/bitvec/blob/main/Prototyping)
   1. 0.22
   2. 0.21
   3. 0.20
   4. 0.19
   5. 0.18
   6. 0.17
   7. 0.16
   8. 0.15
   9. 0.14
   10. 0.13
   11. 0.12
   12. 0.11
   13. 0.10
   14. 0.9
   15. 0.8
   16. 0.7
   17. 0.6
   18. 0.5
   19. 0.4
   20. 0.3
   21. 0.2
   22. 0.1

Version 1

bitvec’s initial development is now complete, and uses the one-dot series. It will continue to receive maintenance, but its API is now stable and will not change until const-generics allow BitArray to be rewritten.

1.1.0

The BitSlice::shift_{left,right} functions have been renamed to BitSlice::shift_{start,end} to try to better reflect their behavior. These functions move data relative to the index as defined by the O: BitOrder type parameter, not according to the processor lsl and lsr instructions.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[senseix21]

Review: safe to merge

Clean bump. Checked the things that could actually bite us:

• Lock-only (+2 / -2): just the bitvec version and checksum. Cargo.toml pins version = "1.0", so 1.1.1 already satisfies the caret — this records the resolution we'd get regardless.
• No transitive churn. bitvec's dependency list is still exactly funty, radium, tap, wyz — unchanged. That matters more than the version number here: funty/radium are where bitvec's historical trouble lived, and neither moves.
• no_std posture intact: bitvec = { version = "1.0", default-features = false, features = ["alloc"] }. Still alloc-only, no std leak into the kernel build.
• CI is fully green — 66 jobs, including build, boot-smoke, attestation, reproducible, the whole dark-features-compile matrix and the proof-crates matrix. For a crate that does bit-level aliasing inside the kernel, boot-smoke + reproducible passing is the evidence I care about, not the diff size.

The only reason to look twice at bitvec at all is its soundness history around aliasing and BitSlice reference semantics. Since 1.0.1 → 1.1.1 moves no dependency and changes no feature, and the boot and reproducibility lanes are green, I'm satisfied.

Approve.