chore(main): release v1.0.0

[github-actions]

Features

• BREAKING: release 1.0.0
• add distance helper function
• initial codebase for PDQ (feat: initial codebase for PDQ #1)

---

PR by releaser-pleaser 🤖

If you want to modify the proposed release, add you overrides here. You can learn more about the options in the docs.

Release Notes

Prefix / Start

This will be added to the start of the release notes.

Suffix / End

This will be added to the end of the release notes.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds CHANGELOG.md documenting a v1.0.0 release with a BREAKING note and two feature bullets: a distance helper and the initial PDQ codebase (issue #1).

Changes

Release v1.0.0 changelog

Layer / File(s)	Summary
Changelog entry for v1.0.0 CHANGELOG.md	Adds CHANGELOG.md with a v1.0.0 release entry, a "BREAKING" note, and feature bullets for a distance helper function and the initial PDQ codebase (issue #1).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A tiny changelog, crisp and new,
v1.0.0 — the rabbit knew.
Distance helper hops in line,
PDQ's first seed begins to shine. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'chore(main): release v1.0.0' clearly and concisely describes the main change: creating a v1.0.0 release with changelog documentation updates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch releaser-pleaser--branches--main

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

CHANGELOG.md (1)

3-3: ⚡ Quick win

Consider adding the release date to follow Keep a Changelog format.

The version header would be more informative with the release date included. The Keep a Changelog format recommends: ## [v0.1.0](link) - 2026-05-14

📅 Proposed addition

-## [v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0)
+## [v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0) - 2026-05-14

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 3, Update the release header line that currently reads
"## [v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0)" to include
the release date in Keep a Changelog format (e.g., change to "##
[v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0) - 2026-05-14"),
ensuring the version header string is modified accordingly.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Line 3: Update the release header line that currently reads "##
[v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0)" to include the
release date in Keep a Changelog format (e.g., change to "##
[v0.1.0](https://github.com/MatthewSH/pdq/releases/tag/v0.1.0) - 2026-05-14"),
ensuring the version header string is modified accordingly.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8d6cf7d3-8170-496f-bde9-c57cbcaab0a6

📥 Commits

Reviewing files that changed from the base of the PR and between 6c0af8f and 88146f8.

📒 Files selected for processing (1)

• CHANGELOG.md

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Line 7: Update the "**BREAKING**: release 1.0.0" changelog entry to include a
concise description of what changed, the impact (which APIs/behaviors are
incompatible), and clear migration steps or examples for consumers;
specifically, replace or augment the existing line "**BREAKING**: release 1.0.0"
with a short summary of the breaking change, list affected
functions/endpoints/modules, provide recommended code changes or a migration
snippet, and optionally link to related docs or issue/PR numbers for more
context.
- Line 3: The CHANGELOG contains "## [v1.0.0]" (and another "v1.0.0" occurrence)
but the PR title/release is v0.1.0; update the version strings in CHANGELOG.md
(replace "v1.0.0" instances such as the heading "## [v1.0.0]" and the other
occurrence on line 7) to the intended release version (e.g., "v0.1.0"), or
alternatively change the PR title/configuration to match the version in
CHANGELOG so both are consistent.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e88210a3-d26c-4172-b5cc-75f894ee5cda

📥 Commits

Reviewing files that changed from the base of the PR and between 5a20116 and f7e79d8.

📒 Files selected for processing (1)

• CHANGELOG.md