Skip to content

deps: bump noyalib from 0.0.58 to 0.0.60 - #434

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/cargo/noyalib-0.0.60
Nov 16, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
dependabot/cargo/noyalib-0.0.60

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps noyalib from 0.0.58 to 0.0.60.

Release notes

Sourced from noyalib's releases.

noyalib 0.0.60

Highlights

  • Historical CI and SAST evidence restored: merged PR #482 had no successful checks after its fork-workflow approval expired. The recovery ran 7,195 tests and CodeQL against its actual source commit, allowing the Scorecard CI-Tests and SAST alerts to close without dismissal.
  • Restricted recovery workflow: remote and local ancestry checks accept only commits already merged into the default branch. Historical tests start from a trusted checkout, use read-only permissions and no build cache. An isolated job records the actual test outcome against the confirmed source SHA. Twenty-two regression tests cover reporting, ancestry and checkout order.
  • CI maintenance: the alloc integration build uses rust-cache 2.9.3 (#516), and Markdown lint uses action 25.0.0 (#517).

The core Rust sources, public API, Cargo features and Rust 1.89.0 minimum remain as in v0.0.59. Existing std and no_std functionality is preserved.

What's Changed

Checksums

SHA-256 of every asset attached to this release:

5d22fa457add2a632cb69db09fb03f914c0b5c9659e8d51e9ff4183b423342d4  SBOM.cdx.json
041a21a7402719c3e5827d2e2817a84ac539b4abee68d17316f9e0c23cf84491  SBOM.cdx.json.asc
4e34b2ac538ee2090d6cf3766c13a42836f1829563e9aa42f5973a5ed5684e2e  SBOM.cdx.json.bundle
ba6bc6a2b3a0e7d9882a9429c72e806383ba12739b06a267bc6960b6c9c0c207  SBOM.txt
dbe7fa6dcc69b7e4dcfcb4b037b55f10871e5e917af60f5c6f102d49f501eca4  SBOM.txt.asc
7f450eff77171ec46fe859ea0beb42d75e3de3068b116bc20913aa19776136ae  SBOM.txt.bundle
8dc7aac9ec569a992f35e39b71177fd3cbc7ee4ecf9f5096edc4808de1554d46  SHA256SUMS.txt
8270d8d46cf0c67dc380d6210695251e86eeb18ba6bf4fadc7f75e598d392677  SHA512SUMS.txt
c4f58e0d7f94aac1ff656e07a05512093b0a0f866f5778f94e84909f50fc3157  noyalib-0.0.60.crate
32b8d1620495f87e410ddf3fd2161bd9619c97a17c46901394affdbdf0b3c09f  noyalib-0.0.60.crate.asc
d841f199f3a94fdb5d006960efacbf45cf19f8b490ae3eb754251c73a2bd8878  noyalib-0.0.60.crate.bundle

Full Changelog: sebastienrousseau/noyalib@v0.0.59...v0.0.60

noyalib 0.0.59

Highlights ⭐️

  • Alloc-only tooling: CST parsing, formatting and editing, property interpolation, recursive Rc anchors, strict string/slice helpers, and recovery work without std. Enabling recovery no longer enables std implicitly; hosted callers must request it when needed.
  • Alloc-only source information: typed AST fallback and document streams retain Spanned<T> locations and error field paths without thread-local storage. Portable behavior tests cover core, accelerated, and combined feature sets; bare-metal gates check the combined portable set.
  • No runtime math dependency (#500): private core float helpers preserve fractional-part and fused multiply-add behavior in alloc-only builds. Both std and no_std consumers can omit libm from their active dependency graph. Existing default features, --no-default-features builds, and the MSRV are unchanged; libm is used only by development oracle tests.
  • no_std unit coverage: all 250 library unit tests pass with the std feature disabled. Host test helpers import std only under cfg(test); a dedicated CI job checks the alloc-only library with an isolated build cache.
  • CST editing, contributed by Zoo Sky (@​zoosky): grow_value grows a scalar into a typed collection with comment preservation and candidate validation. Dash-line insertion places new fields beneath a sequence item's key, including indentless and nested sequences. Both contributions retain Zoo Sky's commit authorship.
  • tokio 1.54.1 retains the RUSTSEC-2026-0386 fix: AsyncFd's safe constructors violated I/O safety in tokio 1.53.2. The update retains the fix introduced in 1.53.3; rustix also moves to 1.1.6, with refreshed publisher evidence for both existing trusted authors.
  • jsonschema 0.60.2 closes a backtracking-limit bypass: unfinished matches now fail closed under not and patternProperties. The engine caches unfinished matches across retries, resolving the repeated-work regression that blocked 0.59. Exhaustion reports one shared engine failure; regression tests cover negation, property constraints and 200 repeated or distinct over-limit subjects.
  • Dependencies and CI: serde-saphyr 2.0.0 for the compare-saphyr benchmarks, schemars 1.2.3, smallvec 1.16.4, arbitrary 1.5.0, tokio-util 0.7.20 and serde_json 1.0.154, with their cargo vet records; the libyaml differential fuzz targets no longer flag NEL, LS and PS, which YAML 1.1 treats as line breaks and YAML 1.2 does not; and the registry drift net's shim probe and npm job are fixed.

What's Changed

... (truncated)

Changelog

Sourced from noyalib's changelog.

[v0.0.60] - 2026-11-10

Fixed

  • Restore missing CI and SAST evidence for merged PR #482 after its fork-workflow approval expired. Historical recovery runs real tests and CodeQL against the verified source commit and reports the actual result.
  • Restrict historical test execution to commits already merged into the default branch. Remote ancestry checks and a local Git check precede selection of historical source; test execution uses read-only permissions and no build cache. A separate job publishes the result with only commit-status write permission.

Changed

  • Update the alloc integration build's rust-cache action to 2.9.3 (#516).
  • Update the Markdown lint action to 25.0.0 (#517).

[v0.0.59] - 2026-11-09

Security

  • jsonschema 0.60.2 rejects unfinished backtracking matches under not and patternProperties (#514). Previously, reaching the regex step limit could bypass those constraints. Regression tests cover both validation entry points. The engine caches unfinished matches across retries, resolving the repeated-work regression that blocked 0.59.
  • tokio 1.54.1 retains the RUSTSEC-2026-0386 fix. AsyncFd's safe constructors violated I/O safety in 1.53.2; cargo audit and cargo deny failed every build with the tokio feature. 1.53.3 is the oldest fixed release on the 1.53 line; cargo vet records its trusted publisher.

Added

  • Allocation-based tooling is available without std. CST parsing, formatting and editing, property interpolation, recursive Rc anchors, and strict string/slice helpers work with alloc. The recovery feature no longer enables std implicitly; callers that need hosted APIs must also enable std. Hosted signatures and default features stay compatible.
  • cst::Document::grow_value grows a scalar into a typed collection (#505, contributed by @​zoosky). It renders block or flow style for the insertion site and verifies the complete candidate before changing the source. Scalar comments and LF, CRLF, or CR line endings are preserved; alias references and shared anchors are refused. Existing collections use the same replacement rules as set_value.

Changed

  • tokio 1.54.1 and rustix 1.1.6, with refreshed publisher evidence for

... (truncated)

Commits
  • 2b39662 chore(release): noyalib v0.0.60
  • 14b85af fix(ci): restore historical test and SAST evidence
  • abcb2fe release: v0.0.59
  • 9424721 feat!: prepare v0.0.59 parser, alloc tooling and schema hardening
  • cc4c867 Merge pull request #504 from sebastienrousseau/feat/v0.0.59
  • b27ae20 ci(deps): move codeql-action/init to 4.38.3 with analyze
  • bf7923b chore(vet): exempt the crate versions from the Dependabot bumps
  • a8edf96 revert(deps): hold jsonschema at 0.58 until the hardening test is ported
  • 2adc89c ci(deps): bump the rust-toolchain group across 1 directory with 3 updates
  • 63dc32c deps(deps): bump smallvec from 1.16.2 to 1.16.4
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [noyalib](https://github.com/sebastienrousseau/noyalib) from 0.0.58 to 0.0.60.
- [Release notes](https://github.com/sebastienrousseau/noyalib/releases)
- [Changelog](https://github.com/sebastienrousseau/noyalib/blob/main/CHANGELOG.md)
- [Commits](sebastienrousseau/noyalib@v0.0.58...v0.0.60)

---
updated-dependencies:
- dependency-name: noyalib
  dependency-version: 0.0.60
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Nov 16, 2026
@github-actions
github-actions Bot merged commit 8ef2e23 into main Nov 16, 2026
2 checks passed
@github-actions
github-actions Bot deleted the dependabot/cargo/noyalib-0.0.60 branch November 16, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update Rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants