Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump yaml from 2.1.3 to 2.2.2 in /pkg/dependency/parser/nodejs/yarn/testcase_deps_generator #6156

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 19, 2024

Bumps yaml from 2.1.3 to 2.2.2.

Release notes

Sourced from yaml's releases.

v2.2.2

This patch release includes a fix for an error that could be thrown in parseDocument for degenerate input. Otherwise, it's a patch release uplifting a few fixes from the ongoing v2.3 work to v2.2:

  • Corner case failure in error pretty-printer (CVE-2023-2251)
  • Use correct argument order when stringifying flow collection comments (#443)
  • First-line folding for block scalars (#422)

v2.2.1

  • Quote top-level map keys containing document markers (#431)

v2.2.0

New Features

  • Add flowCollectionPadding toString option (#420)
  • Use indicator line for props on block collection values of mappings (#425)

Bugfixes

  • Minor relaxation of types for custom tags (#429)
Commits
  • f21fa45 2.2.2
  • 984f578 fix: Corner case failure in error pretty-printer
  • 443e3aa fix: First-line folding for block scalars (fixes #422)
  • 5af5d3d fix: Use correct argument order when stringifying flow collection comments (f...
  • c914dcc 2.2.1
  • c8551eb fix: Quote top-level map keys containing document markers (fixes #431)
  • 3576408 2.2.0
  • ab52daa ci: Remove all @​types except for node when testing types on old TS
  • 85be08d chore: Explicitly set supported types in tsconfig.json
  • 4732502 ci: Uninstall @​jest/types before testing types on TS 4.2
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [yaml](https://github.com/eemeli/yaml) from 2.1.3 to 2.2.2.
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.1.3...v2.2.2)

---
updated-dependencies:
- dependency-name: yaml
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@knqyf263
Copy link
Collaborator

I was looking for an option to disable Dependabot for a specific dir, but didn't find it. Any ideas? @DmitriyLewen
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore

@DmitriyLewen
Copy link
Contributor

I have already looked at this case.
But Dependabot doesn't currently support dir skipping - https://github.com/dependent/dependent-core/issues/4364#issuecomment-1887660591

I am monitoring this issue to see when there will be updates.

But for now it looks like our only option is to update this test dependency.

@knqyf263
Copy link
Collaborator

knqyf263 commented Feb 20, 2024

OK, so I'll close this PR.

BTW, we may want to re-create test cases manually than automatically generating them. Then, we will no longer need this kind of generator. I was concerned about the parser bugs and decided to use real-world files, but it made maintenance harder. I now think we should manually create a file and maintain it.

@DmitriyLewen It would be great if you quickly refactor test data.

@knqyf263 knqyf263 closed this Feb 20, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 20, 2024

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 @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/pkg/dependency/parser/nodejs/yarn/testcase_deps_generator/yaml-2.2.2 branch February 20, 2024 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants