release: v0.3.0 — first crates.io release

[Liohtml]

Prepares the first crates.io release of google-maps-scraper.

Changes

• Bump version 0.2.0 → 0.3.0. The unreleased ScraperConfig::place_panel_jitter field is a breaking addition for code constructing the struct exhaustively (all fields public, no #[non_exhaustive]), so a 0.x minor bump is required, not a patch.
• Remove the publish = false guard from Cargo.toml. Its comment said to remove it once a deliberate release decision is made — this PR is that decision.
• Add documentation = "https://docs.rs/google-maps-scraper" to Cargo.toml.
• Changelog: promote the Unreleased section to [0.3.0] - 2026-07-17 and update the compare links.
• README: install from crates.io (google-maps-scraper = "0.3") instead of git; add crates.io and docs.rs badges; drop the "not yet published" note.
• New .github/workflows/release.yml: pushing a v* tag verifies the tag matches the Cargo.toml version, runs fmt/clippy/tests plus cargo publish --dry-run, publishes to crates.io using the CARGO_REGISTRY_TOKEN secret (in a release environment so approval protection can be added), and creates a GitHub release with notes extracted from the changelog.

Verification

• cargo build, cargo test (9 unit + 1 doc test), cargo fmt --check, cargo clippy --all-targets -D warnings: all pass
• cargo audit: 0 vulnerabilities across 150 dependencies
• cargo publish --dry-run: package builds and uploads cleanly
• Crate name google-maps-scraper verified still free on the crates.io index

After merging

1. Add a crates.io API token (publish scopes) as the CARGO_REGISTRY_TOKEN repository secret.
2. git tag v0.3.0 && git push origin v0.3.0 — the release workflow publishes and creates the GitHub release.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HHcB7Dhren7PSwn4va8BKv

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@Liohtml, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 086629dd-fdfa-4cf5-befc-c51c12597e7c

📥 Commits

Reviewing files that changed from the base of the PR and between 163d8ca and 85b8930.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• .github/workflows/release.yml
• CHANGELOG.md
• Cargo.toml
• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/project-analysis-crates-release-kqf0k9

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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