chore: update all deps#244
Open
lizelive wants to merge 13 commits into
Open
Conversation
Refresh all dependency version requirements to their latest semver-compatible releases (anyhow, serde, log, tracing, byteorder, sha2, plist, clap, and others). No breaking API changes involved. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Migrate to the current rasn ASN.1 codec API: ConstOid was replaced by Oid::const_new returning &'static Oid, EncapsulatedContentInfo::content became Option<Any>, and SetOf grew its own insert-based API in place of a raw BTreeSet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adapt to the current zip API: ZipFile is now generic over its reader (ZipFile<'_, R>), FileOptions was renamed SimpleFileOptions for the common case, and start_file_aligned was folded into start_file via FileOptions::with_alignment. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
pubgrub's DependencyProvider trait was split into separate prioritize and choose_version methods (previously one combined choose_package_version), Version no longer needs a lowest()/bump() trait impl since Ranges<V> now derives VersionSet from plain Ord + Clone + Debug + Display, and Range was renamed to Ranges with richer constructors (lower_than, from_range_bounds) that make the version bump() workaround for inclusive bounds unnecessary. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
PaddingScheme was replaced by concrete SignatureScheme types (Pkcs1v15Sign::new::<D>()), and the PublicKey trait was folded into inherent methods on RsaPublicKey. Also pin appbundle's direct pkcs8 dependency to 0.10.2 so it unifies with the pkcs8 version rsa 0.9 pulls in transitively, rather than creating two incompatible pkcs8 crate instances in the dependency graph. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
base64 0.21 removed the free encode/decode functions in favor of the Engine trait; switch call sites to base64::engine::general_purpose::STANDARD. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…uild
quick-xml's serde integration changed its defaults significantly:
- The `$unflatten=name` prefix for child elements was removed; a plain
field name now maps to a child element by default (mvn's Maven
metadata/pom/dependency structs).
- Scalar fields now serialize as child elements by default instead of
attributes; attributes require an explicit `@name` prefix. This
silently broke every generated AndroidManifest.xml, AppxManifest.xml,
AppxBlockMap.xml, and [Content_Types].xml attribute (e.g. `android:name`,
`Name`, `Hash`) into wrong child elements, since none of those fields
previously needed a prefix to be attributes. Added `@` prefixes
throughout apk/manifest.rs and msix/{manifest,block_map,content_types}.rs
to restore the original attribute-based output, and added regression
tests asserting the attribute form since this was previously untested.
- Heterogeneous "choice" sequences (Vec of an enum where each variant
serializes under its own tag name, e.g. msix's Capability/Rule enums)
now require `#[serde(rename = "$value")]` on the Vec field; introduced
a Capabilities wrapper struct for this in msix's manifest.
- `quick_xml::se::to_writer` now requires `fmt::Write` instead of
`io::Write`; switched msix's byte-buffer writer to `to_utf8_io_writer`.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
indicatif, console, shlex, zstd, reqwest to latest majors in xbuild All of these compiled and passed tests without call-site changes, except reqwest's rustls-tls feature which was renamed to rustls in 0.13. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Image::read_png now requires Read + Seek instead of just Read, so wrap the in-memory PNG buffer in a Cursor. x509-certificate stays pinned at 0.24.0 since apple-codesign 0.29 (the latest release) depends on that exact version; bumping it would create two incompatible x509-certificate crate instances in the graph. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
image::io::Reader was renamed to image::ImageReader, and ImageOutputFormat was replaced by the existing ImageFormat enum used directly with write_to. pem::Pem's tag/contents fields became private accessor methods. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
No call-site changes required. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Also drops a now-unneeded `mut` on Zip::finish left over from the zip 8.x migration, and sets workspace.resolver = "2" (implied by all members being edition 2021) to silence the resolver warning that appeared on every build. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.