chore: align gradata-install to v0.5.0 + CHANGELOG

[Gradata]

Aligns gradata-install npm wrapper version with the Python SDK (both at 0.5.0). Adds a 0.5.0 CHANGELOG entry summarizing ~30 PRs merged since going public.

Changes

• gradata-install/package.json: version 0.1.0 to 0.5.0, adds homepage and bugs fields pointing at Gradata/gradata.
• CHANGELOG.md: replaces placeholder [0.5.0] - 2026-04-10 block with consolidated [0.5.0] - 2026-04-15 entry covering PRs feat: emails + legal pages + auto-deploy CI #27 through fix(license): move LICENSE-NOTICE.md to docs/LICENSING.md #59 (Added / Changed / Fixed / Infrastructure sections, Keep-a-Changelog format).
• docs/RELEASE-v0.5.0-DRAFT.md: release notes + tagging commands for Oliver to use after this PR and PR ci: auto-publish PyPI + npm on v*.*.* tags #60 (publish workflows) merge.

Why

No GitHub Releases exist yet. pyproject.toml was already at 0.5.0 but the npm wrapper was still at 0.1.0. Aligning before the first tag so PyPI and npm ship matching versions.

Not in this PR

• No tag is pushed. Tagging happens after merge, by Oliver, once PR ci: auto-publish PyPI + npm on v*.*.* tags #60 (PyPI + npm publish workflows) also lands. See docs/RELEASE-v0.5.0-DRAFT.md for the exact commands.
• pyproject.toml is untouched — already 0.5.0.
• No src/ or cloud/ code changed.

Verification

• pytest tests/ -x -q locally: 2257 passed, 23 skipped. Docs + version bump is behavior-neutral.

[cloudflare-workers-and-pages]

Deploying gradata-dashboard with    Cloudflare Pages

Latest commit:	05203f0
Status:	✅  Deploy successful!
Preview URL:	https://85b83792.gradata-dashboard.pages.dev
Branch Preview URL:	https://chore-align-versions-v0-5-0.gradata-dashboard.pages.dev

View logs

[coderabbitai]

Warning

Rate limit exceeded

@Gradata has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 3 minutes and 21 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 3 minutes and 21 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: abe43574-3399-42d2-a654-8cd8672b4e1f

📥 Commits

Reviewing files that changed from the base of the PR and between 5fd7215 and 05203f0.

📒 Files selected for processing (3)

• CHANGELOG.md
• docs/RELEASE-v0.5.0-DRAFT.md
• gradata-install/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/align-versions-v0.5.0

---

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

[greptile-apps]

Gradata has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.