chore(release): bump version and deploy packages

[mheob-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@mheob/eslint-config@10.0.0

Major Changes

• #352 (@mheob): Update ESLint dependencies and enhance React and perfectionist configs
  • Bump ESLint to v10, perfectionist to v5, and many other dependencies
  • Add React Server Components support via react-rsc plugin
  • Add type-aware React rules (no-implicit-key, no-leaked-conditional-rendering)
  • Add React naming convention rules (context-name, ref-name, use-state)
  • Update perfectionist sort-imports groups to v5 naming convention
  • Enhance ignores config to support function-based userIgnores and TypeScript file ignoring
  • Add GLOB_ASTRO_TS glob pattern and ignoresTypeAware type option
  • Update generated type definitions for new plugin rules

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
eslint-config	Ready	Preview, Comment	Feb 13, 2026 4:16pm

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (2)

• WIP
• chore(release)

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[claude]

PR Review: Release v10.0.0

This is an automated Changesets release PR that properly packages the changes from #352. Here's my review:

✅ Code Quality & Best Practices

Excellent execution of the Changesets workflow:

• The changeset file (.changeset/update-eslint-deps-and-configs.md) is correctly consumed and removed
• CHANGELOG.md properly updated with comprehensive release notes at packages/eslint-config/CHANGELOG.md:3
• Version bump in package.json follows semantic versioning correctly (9.2.0 → 10.0.0)
• The major version bump is appropriate given the breaking changes (ESLint v10, Perfectionist v5)

Release notes quality:

• Clear, well-structured changelog entry with detailed bullet points
• Properly references the source PR feat(eslint): update deps and configs #352
• Credits the author correctly
• Follows the existing changelog format consistently

✅ Potential Issues

No issues detected:

• All file changes are exactly what's expected from a Changesets release
• No manual edits or unexpected modifications
• The changeset was properly formatted and consumed

✅ Performance Considerations

No performance concerns:

• This is purely a release metadata update
• No code changes in this PR (code changes were in feat(eslint): update deps and configs #352)
• Package size impact was already addressed in the source PR

✅ Security Concerns

No security issues:

• No dependency changes in this PR (dependencies updated in feat(eslint): update deps and configs #352)
• No code execution paths modified
• Standard release process with no elevated risk

Note: There is a Snyk security check failure showing in the PR status. This should be investigated to ensure no known vulnerabilities are being published.

📋 Pre-Merge Checklist

Before merging, verify:

1. ✅ CI checks pass (currently "Check" job is in progress)
2. ⚠️ Snyk security check is failing - investigate this before merging
3. ✅ Vercel preview deployment completes successfully
4. ✅ Ensure you're ready to publish to npm (this will trigger automatic publication)

🎯 Recommendation

Conditional approval: This PR is well-formed and follows proper release practices. However, address the Snyk security failure before merging. Once security checks pass, this is ready to merge and publish.

The Changesets action will automatically publish @mheob/eslint-config@10.0.0 to npm upon merge.