chore(release): 0.11.0

[AmanVarshney01]

Release v0.11.0

Publishes the current main branch, including the telemetry outcome fixes from #77.

Version 0.11.0 is already present in package.json but was never published: #75 and #76 used merge commits, so the release workflow correctly skipped them.

This also updates the generated release-PR instructions to explicitly require squash merging.

Squash-merge this PR. The resulting commit title triggers trusted publishing.

[github-actions]

PR preview published

• Version: 0.11.0-pr.78.270.1
• Tag: pr78
• Run with Bun: bunx create-prisma@pr78
• Run with npm: npx create-prisma@pr78
• Run with Yarn: yarn dlx create-prisma@pr78
• Run with pnpm: pnpm dlx create-prisma@pr78
• Run with Deno: deno run -A --minimum-dependency-age=0 npm:create-prisma@pr78
• Workflow run: https://github.com/prisma/create-prisma/actions/runs/33085988561

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c68a3108-1e1d-49dd-abac-20c9177b6f5c

📥 Commits

Reviewing files that changed from the base of the PR and between 25da772 and 2ccd70e.

📒 Files selected for processing (1)

• scripts/bump-version.ts

Included review availability: 1 review is currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

---

Summary by CodeRabbit

• Documentation
  • Updated release instructions to require squash-merging.
  • Clarified that merge commits are skipped and the squash commit title is used for package publishing.

Walkthrough

The release PR body now requires squash-merging. It states that the release workflow uses the squash commit title for npm trusted publishing and skips releases for merge commits.

Merge Risk: ⚪ Minimal · up to 2ccd7

This is a small, localized release-instruction update with no actionable merge-blocking risk remaining beyond normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains the 0.11.0 release and the required squash merge for trusted publishing.
Title check	✅ Passed	The title clearly identifies the release version and matches the primary change.
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.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-0.11.0

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch codex/release-0.11.0

---

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