chore: prepare stable release

[JounQin]

Summary

• Exit Changesets prerelease mode for the stable release.
• Pin the Changesets release action to v1.9.0.
• Remove npm publish token/provenance env from the release workflow.

Test plan

• nps lint
• nps build
• nps test

Summary by CodeRabbit

• Chores
  • Updated internal release configuration and CI/CD workflow settings.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4021475

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

Name	Type
prettier-eslint	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 40acc42a-9cd2-4733-91f9-33228e0a0ede

📥 Commits

Reviewing files that changed from the base of the PR and between f88b790 and 4021475.

📒 Files selected for processing (2)

• .changeset/pre.json
• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

The .changeset/pre.json mode field is changed from "pre" to "exit", ending the pre-release cycle. The release workflow pins the changesets/action reference to a specific commit SHA and removes the NPM_CONFIG_PROVENANCE and NPM_TOKEN environment variables, retaining only GITHUB_TOKEN.

Changes

Release Configuration Updates

Layer / File(s)	Summary
Exit pre-release mode and tighten workflow .changeset/pre.json, .github/workflows/release.yml	mode is switched from "pre" to "exit" in the changeset config. The release workflow pins changesets/action to a commit SHA and drops NPM_CONFIG_PROVENANCE and NPM_TOKEN, keeping only GITHUB_TOKEN.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Suggested labels

internal

Poem

🐇 Hop, hop, the pre-release is done,
No more "pre" tag under the sun!
We pin our actions, nice and tight,
And trim the tokens left and right.
The rabbit stamps the release page —
Time to exit the pre-release stage! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main objective of the PR—preparing the project for a stable release by exiting prerelease mode.
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 chore/prepare-stable-release

---

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

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/prettier-eslint@1205

commit: 4021475

[JounQin]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Copilot]

Pull request overview

Prepares the repository for a stable release by exiting Changesets prerelease mode and tightening the release workflow’s action version pinning.

Changes:

• Exit Changesets prerelease mode by switching .changeset/pre.json to "mode": "exit".
• Pin changesets/action to a specific commit SHA (v1.9.0).
• Remove npm token/provenance env vars from the release workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/release.yml	Pins the Changesets GitHub Action and adjusts publish-related environment variables.
.changeset/pre.json	Exits prerelease mode to enable stable versioning/releases.

Comments suppressed due to low confidence (1)

.github/workflows/release.yml:47

• The workflow still runs publish: yarn start release (which ultimately runs changeset publish), but the step no longer provides any npm authentication (previously NPM_TOKEN) or provenance/OIDC configuration. As written, publishing to npm is very likely to fail due to missing credentials, causing the release workflow to error on publish runs.

Either (a) restore npm auth/provenance env for this step, or (b) remove/disable the publish: input if the intent is to only open a release PR and not publish from CI.

        with:
          commit: 'chore: release prettier-eslint'
          title: 'chore: release prettier-eslint'
          publish: yarn start release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.