Bump js-yaml and @angular-devkit/build-angular#812
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) to 4.2.0 and updates ancestor dependency [@angular-devkit/build-angular](https://github.com/angular/angular-cli). These dependencies need to be updated together. Updates `js-yaml` from 4.1.0 to 4.2.0 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.0...4.2.0) Updates `@angular-devkit/build-angular` from 14.2.13 to 21.2.16 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@14.2.13...v21.2.16) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.2.0 dependency-type: indirect - dependency-name: "@angular-devkit/build-angular" dependency-version: 21.2.16 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
|
Semgrep found 1 Risk: Affected versions of vite and vite-plus are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor / Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). Vite's server.fs.deny blocklist—which protects sensitive files such as .env and certificate files from being served—can be bypassed on Windows using alternate path representations (NTFS Alternate Data Stream syntax like Manual Review Advice: A vulnerability from this advisory is reachable if you expose the Vite dev server or vite-plus to the network by configuring a non-loopback address using the --host CLI flag on Windows Fix: Upgrade this library to at least version 7.3.5 at angular2-jwt/package-lock.json:400. Reference(s): GHSA-fx2h-pf6j-xcff |
Bumps js-yaml to 4.2.0 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.
Updates
js-yamlfrom 4.1.0 to 4.2.0Changelog
Sourced from js-yaml's changelog.
Commits
590dbab4.2.0 releasedf944dc5Add package.json funding fieldf692719Changelog update9971a06Fix digits in YAML named tag handles464a5b8Fix flow scalar trailing whitespace folding, close #3071fda4f7Tests for #567, #565031ad07Stop resolving numbers with underscores as numeric scalars, #627e46d223CI config update9023feeAdd lockfile990e6f4Docs updateUpdates
@angular-devkit/build-angularfrom 14.2.13 to 21.2.16Release notes
Sourced from @angular-devkit/build-angular's releases.
... (truncated)
Changelog
Sourced from @angular-devkit/build-angular's changelog.
... (truncated)
Commits
1efc647release: cut the v21.2.16 release14459e2build: update dependency webpack-dev-server to 5.2.577c9047fix(@angular/cli): update pacote to 21.5.1d052e97fix(@angular/ssr): prioritize options over environment variables in AngularNo...d318dddrelease: cut the v21.2.15 releasec7a7f19fix(@angular/cli): support registry metadata fetching under bun package managerbdc3d2ftest(@angular/cli): ignore engines in version-specifier E2E test when using yarn42ac0edfix(@angular/cli): remove forceAuth and unscoped credential parsing2c25333test(@angular/cli): remove unscoped authentication test cases from registry t...4488398release: cut the v21.2.14 releaseDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.