deps(ts): bump js-yaml from 5.2.2 to 5.2.3 in /frontend - #130
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(ts): bump js-yaml from 5.2.2 to 5.2.3 in /frontend#130dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 5.2.2 to 5.2.3. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@5.2.2...5.2.3) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.2.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Owner
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/frontend/js-yaml-5.2.3
branch
August 25, 2026 16:10
pacphi
added a commit
that referenced
this pull request
Aug 25, 2026
* chore(deps): consolidate PRs #128-137, fix h2/lru advisories Consolidates 8 of the 11 open Dependabot PRs into a single branch: - deps(rust): serde_json 1.0.150 -> 1.0.151 (#128) - deps(rust): calamine 0.36.0 -> 0.36.1 (#131) - deps(rust): http-body-util 0.1.4 -> 0.1.5 (#132) - deps(ts): js-yaml 5.2.2 -> 5.2.3 (#130) - deps(ts): vite 8.0.16 -> 8.2.1 (#133) - deps(ts): prettier 3.8.3 -> 3.9.6 (#134) - deps(ts): recharts 3.8.1 -> 3.10.1 (#135) - deps(actions): taiki-e/install-action 2.85.8 -> 2.86.3 (#137) Deferred (left open, not applied): - #116/#126 (candle-core/candle-transformers 0.10.2 -> 0.11.0): still blocked on a mistralrs release supporting candle 0.11 (mistralrs is still pinned at 0.8.1); would create duplicate candle-core/candle-nn builds, same as previously deferred in #127. - #136 (@tanstack/react-table 8.21.3 -> 9.1.2): 8.21.3 is still the latest 8.x release, so this is a major-version rewrite, not a patch bump — same situation as previously-deferred #119. Pre-existing/upgrade-caused fixes: - Prettier 3.9 changed union-type-alias wrapping ("don't break union type when it can fit"), which flipped two already-passing files to fail the format-check gate. Reformatted with `prettier --write` (RecurringPage.tsx, models.ts) — no logic changes. Security audit (cargo audit / pnpm audit / GitHub Dependabot alerts): - RUSTSEC-2026-0258 (h2 0.4.14, unbounded empty DATA frames DoS): fixed by bumping h2 to 0.4.16 (in-range lockfile-only update via aws-smithy-http-client/hyper's transitive dependency). - RUSTSEC-2026-0253 (lru 0.16.4, use-after-free risk in LruCache::pop() under panic): no fix available — aws-sdk-s3 (latest 1.143.0 checked) still hard-pins `lru = "^0.16.3"`; the fix requires lru 0.18, a semver-major bump upstream hasn't adopted. Documented and ignored in audit-ignore / .cargo/audit.toml pending an aws-sdk-s3 release. - RUSTSEC-2026-0235 (rkyv 0.7.46, pre-existing ignore): also added to .cargo/audit.toml, which was missing it despite audit-ignore already covering it — brings the two files back in sync. - pnpm audit: no known vulnerabilities. - GitHub Dependabot alerts: 0 open. Verification (mirrors CI exactly): - Frontend: pnpm install --frozen-lockfile, lint, tsc --noEmit, prettier --check, vitest --run, build — all pass. - Backend: cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace (incl. DB integration tests via docker-compose.test.yml) — all pass. - Security: bash .github/scripts/cargo-audit.sh (CI's exact gate) — passes with 9 documented exceptions. * fix(api): box large S3 SdkError variants to satisfy clippy::result_large_err CI's floating `dtolnay/rust-toolchain@stable` action advanced to a newer Rust/clippy since the last green run on main, and the newer clippy now flags StorageError's Err variants (392-432 bytes, dominated by aws_sdk_s3::error::SdkError) under result_large_err. Box each SdkError source field to shrink the enum; no behavior change.
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
1 participant
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 js-yaml from 5.2.2 to 5.2.3.
Changelog
Sourced from js-yaml's changelog.
Commits
67404455.2.3 released94e766dUpdate changelogc3bd7caPolish previous commit, #78000209b6presenter: treat a tab-indented line in a folded scalar as more-indented (#780)40fcb4fFix missing mapping values before document markers and reject unpaired mappin...49280f3Fix !!timestamp resolution for years 0000-0099, #775355dc96fix: prevent prototype fallback in tag and harden object lookups, #782 (than...d524f83docs: add contributing guidelinesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)