fix(ci): repair crates.io package verification - #75
Merged
Conversation
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.
Summary\n- upgrade lbug from 0.17.1 to 0.18.3 so source-build fallback no longer whole-archives duplicate component libraries\n- align bundled JSON and FTS extensions with Ladybug ABI/cache version 0.18.1 on every supported platform\n- link the macOS x86_64 compiler runtime required by the new Ladybug static archive without changing other platforms\n- record and validate the updated release-linking runbooks\n\n## Root cause\nThe cargo publish dry-run fell back to lbug 0.17.1's source build. That build linked liblbug.a and its already-contained component archives with whole-archive, causing duplicate utf8proc and ANTLR symbols.\n\n## Verification\n- cargo publish --dry-run --locked --allow-dirty\n- cargo test --workspace --locked (all product tests pass; the sandbox-only HTTP bind case passed separately outside the sandbox)\n- cargo test -p xtask --locked\n- cargo clippy --workspace --all-targets --all-features --locked -- -D warnings\n- cargo fmt --check\n- cargo run -p xtask -- check-workflows\n- k-wiki recommended validation, link checking, and site build\n- hosted CI publish dry-run, Linux, macOS ARM, and macOS Intel checks pass; Windows is pending on the latest documentation-only head\n