deps(dev): bump aegir from 38.1.8 to 39.0.6 #152
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [aegir](https://github.com/ipfs/aegir) from 38.1.8 to 39.0.6. - [Release notes](https://github.com/ipfs/aegir/releases) - [Changelog](https://github.com/ipfs/aegir/blob/master/CHANGELOG.md) - [Commits](ipfs/aegir@v38.1.8...v39.0.6) --- updated-dependencies: - dependency-name: aegir dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
## [12.1.2](v12.1.1...v12.1.2) (2023-05-15) ### Dependencies * **dev:** bump aegir from 38.1.8 to 39.0.6 ([#152](#152)) ([72bdf8e](72bdf8e))
|
🎉 This PR is included in version 12.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Hi, we use js-mafmt as a transitive dependency in a project with nodejs-mobile (at 16.17.1), but this PR and js-mafmt 12.1.2 broke our installation because of the As far as I understand, updating aegir as a dev dep should not have an impact on this library's usage in runtime, so Node.js 16.x should technically still be able to run js-mafmt 12.1.2. Could you relax the engine range? |
|
Aegir contains commands to align project config across the lib2p/ipld/multiformats/ipfs repos which is why this change was made here. We only run tests on lts node (18.16.0 at the time of writing) so there's no guarantee this will continue to work on node 16. npm normally just prints a warning message for non-compliant engines - do you have some strict validation turned on? |
|
We are using yarn, with no special configurations, so this seems to be the default behavior with yarn. I understand the alignment argument. However, considering that this was an actual breaking change in our project, could the version of this library have reflected that on major num instead of the patch num? |
Bumps aegir from 38.1.8 to 39.0.6.
Release notes
Sourced from aegir's releases.
... (truncated)
Changelog
Sourced from aegir's changelog.
... (truncated)
Commits
716c6eechore(release): 39.0.6 [skip ci]b7ef86cfix: Update required node version to node 18 and npm 8 (#1184)cf690fcchore(release): 39.0.5 [skip ci]4b4b77bfix: downgrade@semantic-release/npmto cjs version (#1253)d0749bechore(release): 39.0.4 [skip ci]dd91980fix: use semantic-release-monorepo fork (#1252)8acdfe9chore(release): 39.0.3 [skip ci]07150fcdeps: bump minimatch from 5.1.6 to 9.0.0 (#1232)584cecadeps: bump p-map from 5.5.0 to 6.0.0 (#1249)f0be0fcchore(release): 39.0.2 [skip ci]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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)