Repository navigation
fix: clear the sweep warnings and move YAML parsing to serde-saphyr - #15
Merged
Merged
Conversation
unsafe-libyaml is unmaintained (RUSTSEC-2024-0449), and serde_yaml_ng has had no release since 2024-05, so the rule loader parses with serde-saphyr. The three builtin rule files parse to identical values under both. hyperi-ci now stamps the version itself, so .releaserc.yaml and scripts/release-prepare.py go. Zig comes from the hash-pinned ziglang wheel instead of a Node 20 action, cargo-zigbuild is pinned, the Scoop push waits for SCOOP_BUCKET_ENABLED until its bucket repo exists, and the docs pass markdownlint.
A rule pack with more than 32 comment lines between rules: and an indentless sequence failed with "too many consecutive comments before resolving collection entry", because serde-saphyr buffers emitted comments against a 32-event budget. Comments are no longer emitted, so they cannot fail the parse. Only true and false read as booleans, and errors carry their position without a rendered snippet, as the rest of the fleet parses YAML. serde_saphyr::Error is 136 bytes, so LoadError::Parse boxes it; clippy's result_large_err failed the quality gate on every function returning LoadError. The Action's curl-pipe-sh install is marked risk accepted at the line: the script comes over TLS from the host that serves the binary, so fetching it first would add no integrity check, and #10 tracks real verification. .hyperi-ci.yaml takes the release: spelling and drops the inert publish.target.
|
Released in v1.5.11 -- https://github.com/hyperi-io/macbash/releases/tag/v1.5.11 |
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.
Clears every warning the last release left on main, and moves YAML parsing off an unmaintained crate.
Done when CI, Cross-build and Package are green with no warnings on the release run.