Skip to content

chore: release v1.0.0 #2144

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

Closed
wants to merge 21 commits into from
Closed

chore: release v1.0.0 #2144

wants to merge 21 commits into from

Conversation

achingbrain
Copy link
Member

This PR is not for merging, just to surface the changes that will go into that release.

When we are ready to release, I will merge this locally, rebase on top of master & push. This should preserve each PR commit that targets this branch.

@achingbrain achingbrain changed the title release v1.0.0 chore: release v1.0.0 Oct 10, 2023
@maschad maschad mentioned this pull request Oct 10, 2023
@achingbrain achingbrain force-pushed the release-v1.0 branch 7 times, most recently from 66fbdb9 to ce6ee74 Compare November 3, 2023 13:49
@achingbrain achingbrain force-pushed the release-v1.0 branch 5 times, most recently from 9a15061 to e99f66b Compare November 8, 2023 11:25
@achingbrain achingbrain linked an issue Nov 10, 2023 that may be closed by this pull request
achingbrain and others added 15 commits November 10, 2023 07:25
Co-authored-by: Chad Nehemiah <[email protected]>
Co-authored-by: Cayman <[email protected]>
Once upon a time these options were intended to cause libp2p to
close connections or search for more peers that support a given
protocol but it was never implemented.

Remove the options since they don't do anything, they may be
restored in future if the functionality is ever required.
Extract the keychain into it's own package.
A [PeerInfo](https://docs.libp2p.io/concepts/fundamentals/peers/#peer-info)
is a libp2p object that combines a PeerID and some Multiaddrs.

We also add a list of protocols. This was a mistake because protocols are
exchanged during Identify but the PeerInfo object is used for peer discovery.

This is evident because we set the protocol list to an empty array everywhere.

PeerInfo is useful for exchanging peer data with other nodes, if we need a
more fleshed-out peer representation we'd use the `Peer` interface from
the peer store.

BREAKING CHANGE: the `.protocols` property has been removed from the `PeerInfo` interface
We have an `isStarted` method on the `Startable` interface but we only
really use it in tests. Our implementations tend to guard on being
started twice so it just adds noise to every implementation.

BREAKING CHANGE: the `isStarted` method has been removed from the `Startable` interface
Removes version config overrides so release-please will give us a
v1 for libp2p.
Splits out UPnP NAT service module.

BREAKING CHANGE: imports from `libp2p/upnp-nat` should be updated to `@libp2p/upnp-nat`
BREAKING CHANGE: imports from `libp2p/ping` must be updated to `@libp2p/ping`
BREAKING CHANGE: imports from `libp2p/identify` need to change to `@libp2p/identify`
BREAKING CHANGE: imports from `libp2p/dcutr` now need to be from `@libp2p/dcutr`
BREAKING CHANGE: imports from `libp2p/plaintext` should be changed to `@libp2p/plaintext`
BREAKING CHANGE: imports from `libp2p/circuit-relay` should be updated to `@libp2p/circuit-relay-v2`
BREAKING CHANGE: imports from `libp2p/fetch` should be updated to `@libp2p/fetch`
Restores tests that need to spin up one or more libp2p nodes to complete.

Eventually most `*.node.js` tests from the libp2p package should migrate here.
Removes the redundant `Service` from perf exports in line with other changes to modules in v1.

BREAKING CHANGE: the `perfService` export is now just `perf`
Refactors all components to accept a `ComponentLogger` that lets us
prefix log lines with peer ids/arbitrary strings, etc.
This was accidentally published as v1 already - the package on npm
was deleted immediately but npm doesn't allow republishing over old
versions no matter how quickly they were deleted.
The timing has changed on these tests has changed to do a release
of `it-foreach` which now does not introduce artificial async when
calling the each method.
@achingbrain
Copy link
Member Author

These commits are all in master now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

refactor: move services to separate packages
2 participants