chore(release): derive the repo slug from the git remote

[gfazioli]

Summary

Propagated from mantine-base-component: release.ts now derives the owner/repo slug for the GitHub release from the origin remote instead of package/package.json → repository, falling back to the package.json field if no remote exists.

Functional no-op for this repo — its repository field is already correct and resolves to the same slug (verified against the real remotes before propagating). The change matters for the template, where that field still points at gfazioli/mantine-led by design, so every template release targeted the wrong repository and died with HTTP 422 … Release.tag_name already exists — which also aborted release:patch before docs:deploy could run.

Kept in sync so the template and the component repos don't drift.

Test plan

• yarn test (syncpack + format + typecheck + lint + jest)

Summary by CodeRabbit

• Bug Fixes
  • Release creation now automatically targets the repository configured as the local Git remote.
  • Added a fallback to the package repository configuration when the remote cannot be determined.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1bf3ca4b-8055-453f-afc9-c5433d9d17e6

📥 Commits

Reviewing files that changed from the base of the PR and between 52f6b54 and 755894e.

📒 Files selected for processing (1)

• scripts/release.ts

---

📝 Walkthrough

Walkthrough

The release script now resolves the GitHub owner/repo target from the local origin remote, falling back to package.json when unavailable. The release flow awaits this resolution before generating notes and creating the release.

Changes

Release repository resolution

Layer / File(s)	Summary
Resolve repository target scripts/release.ts	The release flow asynchronously derives the repository slug from the origin push URL and warns before falling back to package.json repository metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-slug-from-remote

---

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.}