Repository navigation
test(DEN-3945): certify package.kind lint against canonical Zed - #15
Merged
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
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.
Public
*-testcertificate forORESoftware/ores-cli#281.This binds exact product lint blob
e78a7636df785fbf4746436325bbbc8b38d46184, compiles/tests it under Rust 1.95 with warnings denied, and independently installs checksum-pinned Zed v0.3.0. The gate requires a canonical manifest to passzed validateand the same manifest plus[package] kind = "pub-lib-core"to fail.Authority boundary: Zed remains the executable manifest-schema authority. The ores-cli rule is only an incident-derived early-warning lint; it does not reimplement or supersede Zed validation.
Merge only after exact-head stepful green execution. Tracking: DEN-3945 / ores-cli#281.