| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 5.4.3. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.3.1...5.4.3) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.4.3 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
Hi @code-asher! I'm a fellow human (not a clanker). Your time as an open-source maintainer is super valuable. To help save you time when reviewing this PR, I ran an analysis tool that I work on (PatchWave). It combines static analysis + AI to determine if dependency upgrades are safe to merge. You can see the results below. Hope it helps! This PR is safe to mergecode-server was already on js-yaml 5.4.1 before this lockfile-only PR, and its only application use is the still-supported named load API; the PR bumps that copy to 5.4.3 and ESLint's separate v4 copy from 4.3.1 to 4.3.2 (a merge-processing DoS mitigation). The unit and end-to-end checks passed, and the registry records show the same upstream repository and signing key. ✅ Safe to merge (1)
You can see the full report here |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps js-yaml from 4.3.1 to 5.4.3.
ChangelogSourced from js-yaml's changelog.
... (truncated)
CommitsDependabot 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:
You can disable automated security fix PRs for this repo from the Security Alerts page.