chore(deps): bump object from 0.39.1 to 0.40.0

[dependabot]

Bumps object from 0.39.1 to 0.40.0.

Changelog

Sourced from object's changelog.

0.40.0

Released 2026/08/01.

Breaking changes

• Changed many file format struct fields and constants to use newtypes. Newtypes for bit flags have methods such as contains and intersects. Some constants are fields within another newtype and have methods for conversion. The raw values are always accessible by .0. #894 #897 #898 #899 #900 #957 #958 #959 #970

• Updated macho::DyldCacheHeader to dyld-1340. #885

• Deleted SectionKind::Elf and added sh_type field to SectionFlags::Elf. #891

• Added feature gates to variants of FileFlags, SegmentFlags, SectionFlags, SymbolFlags, and RelocationFlags. #891

• Added p_type field to SegmentFlags::Elf. Added n_type field to SymbolFlags::MachO. Added typ and storage_class fields to SymbolFlags::CoffSection. Added n_type field to SymbolFlags::Xcoff. Added reserved2 field to SectionFlags::MachO. #891 #963

• Renamed build::elf::AttributeTag to AttributeScope. #894

• Changed write::elf::Writer::reserve_strtab/reserve_shstrtab/reserve_dynstr and write::coff::Writer::reserve_symtab_strtab to return an Error for null bytes in strings, or table size overflow. #905

• Changed many write::elf::Writer methods to return u64 instead of usize. #909

• Replaced name fields in write::elf::SectionHeader, write::elf::Sym,

... (truncated)

Commits

• 400e64f Release 0.40.0
• a250ec8 Update Cargo.lock
• 9dbccee Update wasmparser and ruzstd dependencies
• bd44487 Add missing BitOr conversions for newtypes (#970)
• 581e658 read/macho: add Segment::section_offsets (#968)
• 584a5bf write/macho: fix writing of code limit fields (#967)
• 4d2f379 write: add from_raw methods for ELF/Mach-O encoder structs (#966)
• 39ca5ce macho: use section flags to determine kind (#965)
• 441d84e macho: fix handling of common symbols (#964)
• 7caf64f macho: add reserved2 field to SectionFlags::MachO (#963)
• Additional commits viewable in compare view

[github-actions]

🔒 0.x MINOR bump — held for manual review. 0.39.1 → 0.40.0: for a 0.x crate the MINOR component is the de-facto major, so this is BREAKING even though Dependabot labels it semver-minor. This gap broke synth twice on ordeal (0.9→0.12 added BvTerm::Urem, breaking every exhaustive match; 0.9→0.16 in #864 landed with no CI run and left main uncompilable). Build EVERY affected feature set (incl. --features z3-solver) and run the full synth-verify suite before merging.

[github-actions]

🔒 0.x MINOR bump — held for manual review. 0.39.1 → 0.40.0: for a 0.x crate the MINOR component is the de-facto major, so this is BREAKING even though Dependabot labels it semver-minor. This gap broke synth twice on ordeal (0.9→0.12 added BvTerm::Urem, breaking every exhaustive match; 0.9→0.16 in #864 landed with no CI run and left main uncompilable). Build EVERY affected feature set (incl. --features z3-solver) and run the full synth-verify suite before merging.

[avrabe]

Disabled auto-merge on this PR manually.

The 0.x-minor hold did fire (two hold comments above), but auto-merge was still ENABLED (SQUASH) and the major-bump-hold label never landed — so the gate announced a hold it did not enforce. Filed as #965.

The hold is right on the merits: object 0.39.1 → 0.40.0 currently fails Test and Clippy. object is load-bearing here — it is what the execution differentials read ELF symtabs with (and what #959 moved disasm_words onto to kill a synth disasm host-dependency), so a breaking bump landing unverified would surface as oracle failures far from the cause.

Per the 0.x-minor rule this needs a full suite green before merging, not just the core required checks — including the feature-gated paths (--features z3-solver), since a feature-gated build hides unhandled match sites.