Bump pkarr from 8.0.1 to 8.0.2

[dependabot]

Bumps pkarr from 8.0.1 to 8.0.2.

Changelog

Sourced from pkarr's changelog.

Release Guide

This document describes the release process for the pkarr repository. All packages follow Semantic Versioning.

Packages

Package	Location	Registry
pkarr	pkarr/Cargo.toml	crates.io
pkarr-relay	relay/Cargo.toml	crates.io
@synonymdev/pkarr	bindings/js/pkg/package.json	npm

pkarr is the primary crate. A single GitHub release publishes all three packages. The npm package uses the same version as pkarr, while pkarr-relay is versioned independently. A major relay release can ship alongside a patch release of pkarr.

Semantic Versioning

Every version bump must follow semver strictly:

• Major -- breaking API changes.
• Minor -- new functionality, backwards-compatible.
• Patch -- bug fixes, no API changes.

Pre-release versions (e.g. 5.1.0-rc.1, 0.1.4-rc.3) are allowed for early testing on npm or crates.io.

Files to Update

1. pkarr/Cargo.toml -- bump version. The GitHub tag must match this version.
2. relay/Cargo.toml -- bump its independent version and update its pkarr dependency requirement to the new pkarr version.
3. bindings/js/pkg/package.json -- set version to the new pkarr version.

Lock file

4. Cargo.lock -- run cargo check (or cargo build) after editing any Cargo.toml so the lock file reflects the new versions. Commit the updated lock file in the same PR.

Release Process

1. Dry run

... (truncated)

Commits

• aa4011c chore: release v8.0.2 (#321)
• aa048a6 chore: release v8.0.2-rc.0 (#320)
• 8a04710 ci(release): publish packages and relay binaries (#319)
• 6b1b160 feat(relay): add --version CLI flag (#318)
• 7c9079b chore(nix): remove Nix flake configuration (#315)
• cc755e4 feat(client): log relay responses (#314)
• 7af0d13 deps: bump the cargo-dependencies group with 19 updates (#313)
• 13c62a3 ci: reuse shared Context7 workflow (#311)
• e2cd1d7 Merge pull request #312 from pubky/chore/track-ci-workflows-main
• 4d36bca chore: track ci-workflows main
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #89.