search

ahmadnassri / action-template-repository-sync

Keep projects in sync with the template repository they came from
MIT License
10 stars 5 forks source link

build(deps): bump yaml from 1.10.2 to 2.1.1 #61

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps yaml from 1.10.2 to 2.1.1.

Release notes

Sourced from yaml's releases.

v2.1.1

No changes in executable code, only TS types.

  • Revert "Use TS named tuple for range (#385)" -- see #393
  • Fix types for compatibility with TS 4.2 and 4.7
  • Add CI workflow for testing published type in a range of TS versions

v2.1.0

Fixes for TypeScript users. Arguably this could've been a patch release as well.

  • Improve/specify/fix TS types for Document & collection access methods (#383)
  • Use TS named tuple for range (#385)
  • Rename internal Document option as _directives to resolve type conflict with ToString options (#389)
  • Update tsc target to ES2020 to match Node.js support
  • Update dev dependencies, including jest 28

v2.0.1

  • Fix tags and anchors on map keys (#378)

v2.0.0

This update has been in the works for the last year and a half. Its prerelease versions have been thoroughly tested by a wide number of users, and I think it's finally ready for "actual" release, for use in the mythical "production".

The breaking changes introduced here are mostly originating from the v1 CST parser having become a rather difficult beast to work with. So it's here rewritten pretty much completely, now with a lexer as a first stage. Along the way, the whole project was rewritten in TypeScript and the export paths and options refactored pretty deeply.

If you've been using the library just via its parse(), parseDocument() and stringify() functions, then it's quite likely that none of the changes affect your experience in any way. However, if you've been doing something more involved, then I would strongly recommend that you review the library's documentation site for the v2 docs.

Going forward, it's finally time to start experimenting with new YAML spec features that may eventually be included in YAML 1.3 and later. Those will be made available by specifying the version: 'next' option. However, beware! Any features available this way may be removed or have their API broken by any minor release of this library, and no compatibility guarantees with other libraries are given. In general, semver compatibility is guaranteed for features that are explicitly included in the documentation; everything else should be considered as internal implementation details.

The following is an overview of the breaking changes and new features introduced in each of the prerelease steps leading up to this release; the individual releases' notes and the PRs will contain more detail, along with specific migration guides.

BREAKING CHANGES

v2.0.0-0

  • Drop deprecated end points, members, options & defaults (#171)
  • Breaking changes to Document & createNode APIs (#186)
  • When creating a mapping from a JS Object, drop undefined values (#173)
  • Retain existing nodes when using set() in mappings & sequences (#185)

v2.0.0-1

  • Improve JSON compatibility (#189)
  • Refactor tag resolve() API (#201)

v2.0.0-3

  • Drop 'yaml/parse-cst' endpoint (#223)
  • Update build configs & minimum supported versions (#224)

v2.0.0-4

... (truncated)

Commits
  • 96c6993 2.1.1
  • 3b35834 ci: Add separate workflow for TS tests
  • 4ff5051 fix: NodeType<T> for older TS versions
  • d63d48d ci: Add typescript test jobs for its older versions
  • 7e9b489 chore: Fix types for TS 4.7
  • 42e527a chore: Refresh lockfile
  • 98a1d5e Revert "feat: Use TS named tuple for range (#385)"
  • 5050494 docs: Document defaultStringType option more explicitly
  • c80d4c2 2.1.0
  • 102ecf1 chore: Update to jest 28
  • 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 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)
dependabot[bot] commented 2 years ago

Looks like yaml is up-to-date now, so this is no longer needed.