Split non-interface packages out from this module #226
Comments
Splits each interface area into it's own module so we can release breaking changes to (for example) the pubsub interface without also having to upgrade single transport module to the new `@libp2p/interfaces` major. Fixes: #226 BREAKING CHANGE: most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages
Splits each interface area into it's own module so we can release breaking changes to (for example) the pubsub interface without also having to upgrade single transport module to the new `@libp2p/interfaces` major. Fixes: #226 BREAKING CHANGE: most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages
Splits each interface area into it's own module so we can release breaking changes to (for example) the pubsub interface without also having to upgrade single transport module to the new `@libp2p/interfaces` major. Fixes: #226 BREAKING CHANGE: most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages
## [@libp2p/interface-compliance-tests-v3.0.0](https://github.com/libp2p/js-libp2p-interfaces/compare/@libp2p/interface-compliance-tests-v2.0.3...@libp2p/interface-compliance-tests-v3.0.0) (2022-06-14) ### ⚠ BREAKING CHANGES * most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages ### Trivial Changes * break modules apart ([#232](#232)) ([385614e](385614e)), closes [#226](#226)
|
🎉 This issue has been resolved in version @libp2p/interface-compliance-tests-v3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-keychain-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-keys-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-peer-id-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [@libp2p/interfaces-v3.0.0](https://github.com/libp2p/js-libp2p-interfaces/compare/@libp2p/interfaces-v2.0.4...@libp2p/interfaces-v3.0.0) (2022-06-14) ### ⚠ BREAKING CHANGES * most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages ### Trivial Changes * break modules apart ([#232](#232)) ([385614e](385614e)), closes [#226](#226)
|
🎉 This issue has been resolved in version @libp2p/interfaces-v3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-connection-encrypter-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-metrics-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-peer-info-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-record-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version @libp2p/interface-address-manager-v1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## @libp2p/interface-connection-v1.0.0 (2022-06-14) ### ⚠ BREAKING CHANGES * most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages ### Trivial Changes * break modules apart ([#232](#232)) ([385614e](385614e)), closes [#226](#226) * release [skip ci] ([357286d](357286d)) * update aegir ([#234](#234)) ([3e03895](3e03895)) * update readmes ([#233](#233)) ([ee7da38](ee7da38))
## [@libp2p/interface-connection-v1.0.1](https://github.com/libp2p/js-libp2p-interfaces/compare/@libp2p/interface-connection-v1.0.0...@libp2p/interface-connection-v1.0.1) (2022-06-14) ### Trivial Changes * **release:** 1.0.0 [skip ci] ([0005492](0005492)), closes [#226](#226) [#234](#234) [#233](#233)
## @libp2p/interface-content-routing-v1.0.0 (2022-06-14) ### ⚠ BREAKING CHANGES * most modules have been split out of the `@libp2p/interfaces` and `@libp2p/interface-compliance-tests` packages ### Trivial Changes * break modules apart ([#232](#232)) ([385614e](385614e)), closes [#226](#226) * release [skip ci] ([357286d](357286d)) * update aegir ([#234](#234)) ([3e03895](3e03895)) * update readmes ([#233](#233)) ([ee7da38](ee7da38))
## [@libp2p/interface-content-routing-v1.0.1](https://github.com/libp2p/js-libp2p-interfaces/compare/@libp2p/interface-content-routing-v1.0.0...@libp2p/interface-content-routing-v1.0.1) (2022-06-14) ### Trivial Changes * **release:** 1.0.0 [skip ci] ([1211753](1211753)), closes [#226](#226) [#234](#234) [#233](#233)
Now that we've shipped the ts re-write, having so many non-interface modules in this monorepo is of dwindling use since we don't need to make big coordinated changes so much now.
All of our interfaces are in the one
libp2p-interfacesmodule which is basically depended on by everything in the libp2p ecosystem, which means if we release a breaking change to one interface (say, the Registrar), we have to go and upgrade loads of unrelated repos (granted dependabot and CI releases make this less of a pain).It would be better to move the non interface related modules out of this repo, and split the
libp2p-interfacesmodule up into multiple modules (one per dir under src for example), and combine the each set of interfaces with it's test suite. Then we can release breaking changes to an interface without having to upgrade everything, everywhere.The text was updated successfully, but these errors were encountered: