Repository navigation
fix: correct Cross build directory for LSP RC5 - #977
Merged
Merged
Conversation
Contributor
Documentation PreviewYour documentation changes have been deployed to: This preview will be available until the PR is closed. |
Contributor
Documentation PreviewYour documentation changes have been deployed to: This preview will be available until the PR is closed. |
This branch was successfully deployed
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
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.
RC4's musl lanes failed before compilation because the pinned Cross wrapper forwarded the host's absolute
CARGO_BUILD_BUILD_DIRinto a container where onlyCARGO_TARGET_DIRwas remapped to/target. Omit the redundant build-directory override only for Cross subprocesses, preserving native command environments and filesystem permissions.Advance only the server manifest, lock and release allowlist to
1.22.0-rc.5for a new immutable release. Core remains1.23.1; the published RC4 crate and tag stay unchanged. No LSP runtime implementation changes.Validation:
The normal CI/release workflow must qualify and publish RC5 before its binaries are considered released.