chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates#266
chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates#266dependabot[bot] wants to merge 3 commits into
Conversation
…dates Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml). Updates `js-yaml` from 4.1.1 to 5.2.1 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.1...5.2.1) Updates `linkify-it` from 5.0.0 to 5.0.2 - [Changelog](https://github.com/markdown-it/linkify-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/linkify-it@5.0.0...5.0.2) Updates `markdown-it` from 14.1.1 to 14.3.0 - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/markdown-it@14.1.1...14.3.0) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.2.1 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: linkify-it dependency-version: 5.0.2 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: markdown-it dependency-version: 14.3.0 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. OpenSSF ScorecardScorecard details
Scanned Files
|
The latest CodeQL YAML extractor generates yaml_comments trap data, but iac.dbscheme was missing the yaml_comments relation definition. This caused a CatastrophicError during trap file import which cascaded into VALUE_NOT_IN_TYPE errors and test failures across all YAML-based tests. - Added yaml_comments relation to iac.dbscheme - Updated @yaml_locatable to include @yaml_comment Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
Fixed in commit The CI failures were caused by the latest CodeQL YAML extractor generating Two changes were made to
|
|
@copilot still failing after latest charge |
Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
Fixed in commit The yaml/ast failure was a schema fingerprint mismatch: my first fix added Root cause: the pinned The fix updates Two source file updates were also required for the new codeql-extractor API: |
Bumps the npm_and_yarn group with 1 update in the / directory: js-yaml.
Updates
js-yamlfrom 4.1.1 to 5.2.1Changelog
Sourced from js-yaml's changelog.
... (truncated)
Commits
ac16b425.2.1 released4a864e5Deps bump39f3211!!omap: addMapsupport and remove quadratic complexityff17f1eChangelog update8ed15f1deps bump1a562dcFix changelog linkc28ed5e5.2.0 released125cd5aAddmaxAliasesoption3105455ReplacemaxMergeSeqLengthoption withmaxTotalMergeKeys(more robust)39d00d6numbers: Drop boxed numbers support, simplify .identify() checks, clarify rou...Updates
linkify-itfrom 5.0.0 to 5.0.2Changelog
Sourced from linkify-it's changelog.
Commits
50a0c915.0.2 releasedde3b885Update package hooks13effaaAdd package lock39d748dBump c800ce877Drop tlds depsecde823Update benchmark to mitata23c62cdRefactor demo / doc build and publishfd63f3bCI config updatef4ea5afdemo: update bootstrap & layout1454fb6lint: dim warningsUpdates
markdown-itfrom 14.1.1 to 14.3.0Changelog
Sourced from markdown-it's changelog.
Commits
ff0ee0814.3.0 released52e2749Bump linkify-it / vite deps56c2404fix: keep backslash-space hard line break (CommonMark 6.7) (#1185)0fbb18bBump vite from 8.0.14 to 8.0.16 (#1181)83450e2Rework benchmark deps and bump versions57a6863benchmark => tinybench7608db1Update CI config9d8eb42Added package-lock and updated versions to latest possible0aee70dlint: enable@stylistic/no-multi-spacesrule8878985lint => neostandardDependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.