rajasegar / ember-gen-uml

A CLI to generate Plant UML compatible diagrams for Ember components
MIT License
5 stars 1 forks source link

chore(deps-dev): bump semantic-release, @semantic-release/changelog and @semantic-release/git #56

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps semantic-release, @semantic-release/changelog and @semantic-release/git. These dependencies needed to be updated together. Updates semantic-release from 17.4.7 to 18.0.0

Release notes

Sourced from semantic-release's releases.

v18.0.0

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

v18.0.0-beta.8

18.0.0-beta.8 (2021-09-17)

Bug Fixes

  • plugins: upgraded to stable versions of the plugins (d5be46e)

v18.0.0-beta.7

18.0.0-beta.7 (2021-09-03)

Bug Fixes

  • plugins: upgraded to the beta versions of the commit-analyzer and release-notes-generator plugins (d945374)

v18.0.0-beta.6

18.0.0-beta.6 (2021-09-03)

Bug Fixes

  • npm: upgraded to the beta version of the npm plugin (#2103) (995469f)

v18.0.0-beta.5

18.0.0-beta.5 (2021-09-03)

Bug Fixes

  • error: upgraded to the beta of the error plugin (10fb716)

v18.0.0-beta.4

18.0.0-beta.4 (2021-09-03)

Bug Fixes

  • release-notes-generator: updated to the beta of the plugin (5c68d20), closes #2055

v18.0.0-beta.3

... (truncated)

Commits
  • 66cc2b4 feat(node-version): raised the minimum required version to v14.17 (#2132)
  • 1632e1a chore(deps): update dependency dockerode to v3.3.1 (#2113)
  • 0390af3 chore(deps): update dependency sinon to v11.1.2 (#2108)
  • e58b76e chore(deps): update dependency nock to v13.1.3 (#2107)
  • 5e228a1 chore(deps): update dependency codecov to v3.8.3 (#2106)
  • 23d2bc2 docs: fix broken link on github actions recipe (#2102)
  • b4200b0 ci(test): set node version explicitly in test job (#2092)
  • See full diff in compare view


Updates @semantic-release/changelog from 5.0.1 to 6.0.1

Release notes

Sourced from @​semantic-release/changelog's releases.

v6.0.1

6.0.1 (2021-10-30)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v3 (#167) (ef37296)

v6.0.0

6.0.0 (2021-09-22)

Features

  • node-version: raised the minimum required version to v14.17 (#170) (5cf74e4)

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17
Commits
  • ef37296 fix(deps): update dependency @​semantic-release/error to v3 (#167)
  • 03bb179 chore(deps): lock file maintenance (#177)
  • 130705f chore(deps): lock file maintenance (#176)
  • 9c030e8 chore(deps): lock file maintenance (#175)
  • 0a21d3e docs(configuration): Fix incorrect link (#174)
  • 87be8e3 chore(deps): lock file maintenance (#172)
  • afe48aa chore(deps): lock file maintenance (#171)
  • 5cf74e4 feat(node-version): raised the minimum required version to v14.17 (#170)
  • 8f008ce chore(deps): lock file maintenance (#169)
  • 8061852 build(test.yml): set node-version to 16
  • Additional commits viewable in compare view


Updates @semantic-release/git from 9.0.1 to 10.0.1

Release notes

Sourced from @​semantic-release/git's releases.

v10.0.1

10.0.1 (2021-10-30)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v3 (#295) (3e934d4)

v10.0.0

10.0.0 (2021-09-20)

Features

  • node-version: raised the minimum required version to v14.17 (7ab65f8)

BREAKING CHANGES

  • node-version: the minimum required version of node is now v14.17
Commits
  • 3e934d4 fix(deps): update dependency @​semantic-release/error to v3 (#295)
  • 01aad76 chore(deps): lock file maintenance (#304)
  • eae607b chore(deps): lock file maintenance (#302)
  • f9e1a09 chore(deps): lock file maintenance (#301)
  • 51280ff chore(deps): lock file maintenance (#300)
  • 7a41029 chore(deps): lock file maintenance (#299)
  • 7ab65f8 feat(node-version): raised the minimum required version to v14.17
  • 9105df6 chore(deps): lock file maintenance (#296)
  • fccf23d build(release.yml): set node-version to 16
  • 9d20879 chore(deps): lock file maintenance (#294)
  • Additional commits viewable in compare view


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

OK, I won't notify you again about this release, but will get in touch when a new version is available.

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