-
-
Notifications
You must be signed in to change notification settings - Fork 54
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 and semantic-release #380
chore(deps): bump yaml and semantic-release #380
Conversation
Removes [yaml](https://github.com/eemeli/yaml). It's no longer used after updating ancestor dependency [semantic-release](https://github.com/semantic-release/semantic-release). These dependencies need to be updated together. Removes `yaml` Updates `semantic-release` from 19.0.3 to 21.0.1 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v19.0.3...v21.0.1) --- updated-dependencies: - dependency-name: yaml dependency-type: indirect - dependency-name: semantic-release dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Here is the entire list of breaking changes on v20.0.0 21.0.0 (2023-03-24) |
I don't fully understand if this affects us. We do have projects that are ESM and others that are CommonJS.
CI do not install node v18 but 14 in this case
Relates to the previous point.
We already use cc @derberg |
actually asyncapi/.github#205 must be done to remove semantic-release from package.json, and other related dependencies and use the latest release configuration |
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Removes yaml. It's no longer used after updating ancestor dependency semantic-release. These dependencies need to be updated together.
Removes
yaml
Updates
semantic-release
from 19.0.3 to 21.0.1Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
4bddb37
fix(deps): update dependency env-ci to v9 (#2757)aa90774
chore(deps): update dependency testdouble to v3.17.2 (#2751)d7e14f6
docs(artifactory): removed details about using artifactory with legacy auth4a943a5
chore(deps): pin dependencies (#2744)f47a510
chore(deps): lock file maintenance (#2737)05596bc
chore(deps): update dependency prettier to ^2.8.4 (#2746)c6e84ef
chore(deps): update dependency sinon to v15.0.3 (#2748)0cbe804
chore(deps): update dependency fs-extra to ^11.1.0 (#2745)ea32d10
chore(deps): update dependency testdouble to v3.17.1 (#2740)deb1b7f
Merge pull request #2741 from semantic-release/betaDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.