Update docs

[d33bs]

Summary by CodeRabbit

• Documentation
  • Updated README installation instructions to reference the new repository location for release assets and verification examples.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7fd58ee1-2e2a-4e32-bf55-6ff044b444e5

📥 Commits

Reviewing files that changed from the base of the PR and between a4113ed and d1e62f9.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

README documentation updated to reference GitHub Release assets from the new repository owner (wayscience/duckdb_zarr instead of d33bs/duckdb_zarr). Installation URLs and verification examples were updated to reflect the ownership change while preserving asset filenames and version tags.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Updated all GitHub Release asset URLs and installation instructions to reference the new repository owner, replacing d33bs/duckdb_zarr with wayscience/duckdb_zarr. Asset filenames and version tags remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, a skip, the URLs dance,
From d33bs to wayscience, a new stance!
Release notes gleam in GitHub's light,
The rabbit applauds this tidy delight! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update docs' is vague and generic; it doesn't specify which documentation was updated or why, making it unclear from the title alone that the change involves repository ownership updates.	Consider a more descriptive title such as 'Update README with new repository ownership' or 'Update README URLs to reference wayscience/duckdb_zarr' to clearly communicate the specific documentation changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch name-changes

---

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 and usage tips.}