chore: release v0.33.1

[guillaumemichel]

No description provided.

[github-actions]

Suggested version: 0.33.1

Comparing to: v0.33.0 (diff)

Changes in configuration file(s):

(empty)

gorelease says:

# github.com/libp2p/go-libp2p-kad-dht/providers
## incompatible changes
NewProviderManager: changed from func(context.Context, github.com/libp2p/go-libp2p/core/peer.ID, github.com/libp2p/go-libp2p/core/peerstore.Peerstore, github.com/ipfs/go-datastore.Batching, ...Option) (*ProviderManager, error) to func(github.com/libp2p/go-libp2p/core/peer.ID, github.com/libp2p/go-libp2p/core/peerstore.Peerstore, github.com/ipfs/go-datastore.Batching, ...Option) (*ProviderManager, error)

# github.com/libp2p/go-libp2p-kad-dht/rtrefresh
## incompatible changes
NewRtRefreshManager: changed from func(context.Context, github.com/libp2p/go-libp2p/core/host.Host, *github.com/libp2p/go-libp2p-kbucket.RoutingTable, bool, func(cpl uint) (string, error), func(ctx context.Context, key string) error, func(ctx context.Context, p github.com/libp2p/go-libp2p/core/peer.ID) error, time.Duration, time.Duration, time.Duration, chan struct{}) (*RtRefreshManager, error) to func(github.com/libp2p/go-libp2p/core/host.Host, *github.com/libp2p/go-libp2p-kbucket.RoutingTable, bool, func(cpl uint) (string, error), func(ctx context.Context, key string) error, func(ctx context.Context, p github.com/libp2p/go-libp2p/core/peer.ID) error, time.Duration, time.Duration, time.Duration, chan struct{}) (*RtRefreshManager, error)

# diagnostics
required module github.com/microcosm-cc/[email protected] retracted by module author: Retract older versions as only latest is to be depended upon

# summary
Suggested version: v0.34.0

gocompat says:

HEAD is now at 010ef38 chore: release v0.33.0 (#1083)
Previous HEAD position was 010ef38 chore: release v0.33.0 (#1083)
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.