chore(release): 0.7.1

[AmanVarshney01]

Release v0.7.1

This PR bumps create-prisma to 0.7.1.

When this PR merges, GitHub Actions publishes to npm using trusted publishing.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Version updated to 0.7.1

Walkthrough

The version field in package.json is incremented from 0.7.0 to 0.7.1. No other files or declarations are modified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(release): 0.7.1' clearly and directly describes the main change: a version bump release to 0.7.1, which matches the package.json modification.
Description check	✅ Passed	The description is directly related to the changeset, explaining the release of version 0.7.1 and the automated npm publishing process that occurs upon merge.
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.

_{✏️ 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 release/v0.7.1

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch release/v0.7.1

---

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

[github-actions]

PR preview published

• Version: 0.7.1-pr.49.151.1
• Tag: pr49
• Run with Bun: bunx create-prisma@pr49
• Run with npm: npx create-prisma@pr49
• Run with Yarn: yarn dlx create-prisma@pr49
• Run with pnpm: pnpm dlx create-prisma@pr49
• Run with Deno: deno run -A npm:create-prisma@pr49
• Workflow run: https://github.com/prisma/create-prisma/actions/runs/28039884702

[coderabbitai]

Actionable comments posted: 1

🤖 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 `@package.json`:
- Line 3: The package.json specifies version 0.7.1, but the current commit lacks
a corresponding git tag, which will cause the publish workflow to fail at the
"Verify package version matches commit" step. Create a git tag named v0.7.1
pointing to the current commit and push it to the remote repository to ensure
the git tag matches the version number specified in package.json.

🪄 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f1ed3a53-b671-4d92-9d98-ecc899bb6929

📥 Commits

Reviewing files that changed from the base of the PR and between 5d6250a and 89d2f27.

📒 Files selected for processing (1)

• package.json