deps(deps): bump toml from 0.8.23 to 1.1.2+spec-1.1.0 - #727
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(deps): bump toml from 0.8.23 to 1.1.2+spec-1.1.0#727dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
3 tasks
Bumps [toml](https://github.com/toml-rs/toml) from 0.8.23 to 1.1.2+spec-1.1.0. - [Commits](toml-rs/toml@toml-v0.8.23...toml-v1.1.2) --- updated-dependencies: - dependency-name: toml dependency-version: 1.1.2+spec-1.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/toml-1.1.2spec-1.1.0
branch
from
May 13, 2026 04:19
0c1e50a to
faf226d
Compare
proggeramlug
added a commit
that referenced
this pull request
May 13, 2026
Bundles seven green dependabot bumps into a single commit instead of seven round-trips through the PR queue. Renumbered from v0.5.892 to v0.5.893 after rebasing on main — #734 landed v0.5.892 while this batch was in review. Cargo crates: - scraper 0.19.1 → 0.27.0 (#731) — perry-ext-cheerio, perry-stdlib - gstreamer 0.23.7 → 0.25.2 (#730) — perry-ui-gtk4 - bcrypt 0.15 → 0.17 (#728) — perry-stdlib (aligns with perry-ext-bcrypt which already pinned 0.17, so the workspace now resolves a single bcrypt version) GitHub Actions: - actions/download-artifact v4 → v8 (#724) - actions/setup-node v4 → v6 (#725) - actions/cache v4 → v5 (#726) (test.yml line 110's comment referencing v4 is left as-is — it is documenting historical state, not configuring a step.) NPM test fixture: - drizzle-orm ^0.36.0 → ^0.45.2 (#723) in tests/release/packages/drizzle-sqlite/ PR #723 had a stale security-audit FAILURE from a transient advisory-db hit on May 12; main's subsequent run against the unchanged Cargo.lock passed on May 13. The PR only touches npm test fixtures so the audit result was unrelated to its diff. Skipped (real breakage, not safe — being addressed separately): - toml 0.8.23 → 1.1.2+spec-1.1.0 (#727) — major version breaks well_known_bindings.toml parsing; 7 cargo tests + 31 compile-smoke failures. - deno_core 0.311.0 → 0.400.0 (#729) — 89-patch jump, parity + compile-smoke failures from API-breaking changes.
proggeramlug
added a commit
that referenced
this pull request
May 13, 2026
Bundles seven green dependabot bumps into a single commit instead of seven round-trips through the PR queue. Cargo crates: - scraper 0.19.1 → 0.27.0 (#731) — perry-ext-cheerio, perry-stdlib - gstreamer 0.23.7 → 0.25.2 (#730) — perry-ui-gtk4 - bcrypt 0.15 → 0.17 (#728) — perry-stdlib (aligns with perry-ext-bcrypt which already pinned 0.17, so the workspace now resolves a single bcrypt version) GitHub Actions: - actions/download-artifact v4 → v8 (#724) - actions/setup-node v4 → v6 (#725) - actions/cache v4 → v5 (#726) (test.yml line 110's comment referencing v4 is left as-is — it is documenting historical state, not configuring a step.) NPM test fixture: - drizzle-orm ^0.36.0 → ^0.45.2 (#723) in tests/release/packages/drizzle-sqlite/ PR #723 had a stale security-audit FAILURE from a transient advisory-db hit on May 12; main's subsequent run against the unchanged Cargo.lock passed on May 13. The PR only touches npm test fixtures so the audit result was unrelated to its diff. Skipped (real breakage, not safe): - toml 0.8.23 → 1.1.2+spec-1.1.0 (#727) — major version breaks well_known_bindings.toml parsing; 7 cargo tests + 31 compile-smoke failures. - deno_core 0.311.0 → 0.400.0 (#729) — 89-patch jump, parity + compile-smoke failures from API-breaking changes. Rebased onto main at e8c4a95 (HarmonyOS Chart + TreeView shipped as v0.5.893 after #734 shipped as v0.5.892); this commit moves the batch roll-up to v0.5.894 to avoid the patch-version collision.
proggeramlug
added a commit
that referenced
this pull request
May 13, 2026
Bundles seven green dependabot bumps into a single commit instead of seven round-trips through the PR queue. Cargo crates: - scraper 0.19.1 → 0.27.0 (#731) — perry-ext-cheerio, perry-stdlib - gstreamer 0.23.7 → 0.25.2 (#730) — perry-ui-gtk4 - bcrypt 0.15 → 0.17 (#728) — perry-stdlib (aligns with perry-ext-bcrypt which already pinned 0.17, so the workspace now resolves a single bcrypt version) GitHub Actions: - actions/download-artifact v4 → v8 (#724) - actions/setup-node v4 → v6 (#725) - actions/cache v4 → v5 (#726) (test.yml line 110's comment referencing v4 is left as-is — it is documenting historical state, not configuring a step.) NPM test fixture: - drizzle-orm ^0.36.0 → ^0.45.2 (#723) in tests/release/packages/drizzle-sqlite/ PR #723 had a stale security-audit FAILURE from a transient advisory-db hit on May 12; main's subsequent run against the unchanged Cargo.lock passed on May 13. The PR only touches npm test fixtures so the audit result was unrelated to its diff. Skipped (real breakage, not safe): - toml 0.8.23 → 1.1.2+spec-1.1.0 (#727) — major version breaks well_known_bindings.toml parsing; 7 cargo tests + 31 compile-smoke failures. - deno_core 0.311.0 → 0.400.0 (#729) — 89-patch jump, parity + compile-smoke failures from API-breaking changes. Rebased onto main at e8c4a95 (HarmonyOS Chart + TreeView shipped as v0.5.893 after #734 shipped as v0.5.892); this commit moves the batch roll-up to v0.5.894 to avoid the patch-version collision.
4 tasks
proggeramlug
added a commit
that referenced
this pull request
May 13, 2026
….5.899) The two bumps that the v0.5.894 batch deferred as too-disruptive. Addressed with focused migrations. ## toml 1.x `<toml::Value as FromStr>` (called implicitly by `.parse::<toml::Value>()`) is no longer a document parser — it now parses inline values only. Four callsites swapped to `toml::from_str::<toml::Value>(s)` (still document parser): - crates/perry/src/commands/compile/well_known.rs:100 - crates/perry/src/commands/run.rs:343,829,1453 - crates/perry/src/commands/native/validate.rs:164 Restores 7 well_known + validate tests and 31 compile-smoke regressions. ## deno_core 0.400 (v8 0.106 → 147.4.0) API changes migrated in perry-jsruntime (5 source files + Cargo.toml): - `v8::HandleScope` → `v8::PinScope<'_,'_>` - `JsRuntime::handle_scope()` → `deno_core::scope!(scope, &mut runtime)` - `v8::TryCatch::new(scope)` → `v8::tc_scope!(tc_scope, scope)` - `Local<v8::String>::write_utf8` → `write_utf8_v2(buf, WriteFlags)` - `anyhow::Error` → `deno_error::JsErrorBox` for op2 errors - `extension!`'s `init_ops()` → `init()` - `ModuleLoader::load` 4 params → 5 (new `ModuleLoadOptions` shape) - `ModuleLoader::resolve` returns `ModuleLoaderError` FFI surfaces preserved — perry-runtime/codegen/commands unchanged. ## Stack-limit override removed Pre-bump `JsRuntimeState::new` called `Isolate::SetStackLimit` via the Itanium-mangled `_ZN2v87Isolate13SetStackLimitEm` (since v8 0.106 didn't expose it in the Rust bindings). After the bump, calling that symbol while the isolate is not entered silently exits the process with exit code 0 — v8 147's stack-guard aborts cleanly instead of crashing. That's what was killing the three parity tests (test_issue_248_phase2_js_interop, test_issue_248_phase2b_js_callback, test_issue_255_jsruntime_reentrancy) — every test that loaded a .js module called js_runtime_init → JsRuntimeState::new → silent exit. Removed the manual override entirely; v8 147 picks a sane default stack limit from the calling thread's bounds and deno_core::scope! pins the isolate properly for each work scope. ## Validation - cargo build --release -p perry-jsruntime -p perry-runtime -p perry-stdlib -p perry clean - cargo test --release -p perry --bin perry — 152/0 - cargo fmt --all -- --check clean - All three previously-failing parity tests byte-equal Node
proggeramlug
added a commit
that referenced
this pull request
May 13, 2026
….5.899) (#744) The two bumps that the v0.5.894 batch deferred as too-disruptive. Addressed with focused migrations. ## toml 1.x `<toml::Value as FromStr>` (called implicitly by `.parse::<toml::Value>()`) is no longer a document parser — it now parses inline values only. Four callsites swapped to `toml::from_str::<toml::Value>(s)` (still document parser): - crates/perry/src/commands/compile/well_known.rs:100 - crates/perry/src/commands/run.rs:343,829,1453 - crates/perry/src/commands/native/validate.rs:164 Restores 7 well_known + validate tests and 31 compile-smoke regressions. ## deno_core 0.400 (v8 0.106 → 147.4.0) API changes migrated in perry-jsruntime (5 source files + Cargo.toml): - `v8::HandleScope` → `v8::PinScope<'_,'_>` - `JsRuntime::handle_scope()` → `deno_core::scope!(scope, &mut runtime)` - `v8::TryCatch::new(scope)` → `v8::tc_scope!(tc_scope, scope)` - `Local<v8::String>::write_utf8` → `write_utf8_v2(buf, WriteFlags)` - `anyhow::Error` → `deno_error::JsErrorBox` for op2 errors - `extension!`'s `init_ops()` → `init()` - `ModuleLoader::load` 4 params → 5 (new `ModuleLoadOptions` shape) - `ModuleLoader::resolve` returns `ModuleLoaderError` FFI surfaces preserved — perry-runtime/codegen/commands unchanged. ## Stack-limit override removed Pre-bump `JsRuntimeState::new` called `Isolate::SetStackLimit` via the Itanium-mangled `_ZN2v87Isolate13SetStackLimitEm` (since v8 0.106 didn't expose it in the Rust bindings). After the bump, calling that symbol while the isolate is not entered silently exits the process with exit code 0 — v8 147's stack-guard aborts cleanly instead of crashing. That's what was killing the three parity tests (test_issue_248_phase2_js_interop, test_issue_248_phase2b_js_callback, test_issue_255_jsruntime_reentrancy) — every test that loaded a .js module called js_runtime_init → JsRuntimeState::new → silent exit. Removed the manual override entirely; v8 147 picks a sane default stack limit from the calling thread's bounds and deno_core::scope! pins the isolate properly for each work scope. ## Validation - cargo build --release -p perry-jsruntime -p perry-runtime -p perry-stdlib -p perry clean - cargo test --release -p perry --bin perry — 152/0 - cargo fmt --all -- --check clean - All three previously-failing parity tests byte-equal Node
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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.
Bumps toml from 0.8.23 to 1.1.2+spec-1.1.0.
Commits
a3d0047chore: Releasecc37615docs: Update changelog7f5e9e1fix(parser): Consolidate invalid unquoted key into one error (#1138)52feb90fix(parser): Consolidate invalid unquoted key into one erroraad85d4chore(deps): Update j178/prek-action action to v2 (#1136)8b1ac44chore(deps): Update compatible (dev) (#1135)9effd79chore(deps): Update j178/prek-action action to v29db8aadchore: Releasee55a663docs: Update changelogc11d7d7Optimisations (#1133)