Update dependency aegir to v43 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
aegir	^42.2.11 -> ^43.0.0

---

Release Notes

ipfs/aegir (aegir)

v43.0.1

Compare Source

Bug Fixes

• downgrade conventional-changelog-conventionalcommits (3d063ce)

v43.0.0

Compare Source

⚠ BREAKING CHANGES

• if using aegir release in the scripts of a monorepo package, config must be updated:

1. Change "release": "aegir release" in the monorepo root to "release": "aegir run release"
2. Add "release": "aegir release" to each monorepo package
3. Add semantic release config to each monorepo package

Bug Fixes

• remove unused types that break compilation (#​1535) (a020beb)
• revert to semantic-release-monorepo (#​1536) (00bebd4)
• update check-project to use semantic-release-monorepo again (#​1537) (aa65b02)
• use semantic-release beta release (#​1539) (a16e7c2)

Dependencies

• bump @​semantic-release/commit-analyzer from 11.1.0 to 12.0.0 (#​1484) (9f10341)
• bump @​semantic-release/github from 9.2.6 to 10.0.3 (#​1497) (295fa01)
• bump @​semantic-release/npm from 11.0.3 to 12.0.0 (#​1483) (0ab5632)
• bump @​semantic-release/release-notes-generator from 12.1.0 to 13.0.0 (#​1489) (db9e2e7)
• bump conventional-changelog-conventionalcommits from 7.0.2 to 8.0.0 (#​1518) (a566958)
• bump esbuild from 0.20.2 to 0.21.1 (#​1520) (74ff688)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @lassi-js/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from [email protected]
npm ERR! node_modules/typescript-eslint
npm ERR!   dev typescript-eslint@"^7.8.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-31T20_51_08_061Z-debug-0.log