Skip to content

Version Packages - #285

Merged
TheCodeDestroyer merged 1 commit into
mainfrom
changeset-release/main
Sep 22, 2026
Merged

Version Packages#285
TheCodeDestroyer merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 14, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

  • #289 85e7fb9 Thanks @renovate! - chore(deps): update dependency tsup to v8.5.1

  • #308 a01b656 Thanks @TheCodeDestroyer! - fix: Remove package entry points that point to files the build does not create

    • eslint-config-next and eslint-config-a11y: remove the ./rule-overrides export. These packages have no rules file, so the import always failed.
    • Presets: remove the require export and point main to the ESM file. The build makes ESM only, so the .cjs file never existed.
    • tsup-config: point main to the ESM file for the same reason.

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

  • #288 7dbd7ef Thanks @renovate! - fix(deps): update dependency @next/eslint-plugin-next to v16.0.2

  • #289 85e7fb9 Thanks @renovate! - chore(deps): update dependency tsup to v8.5.1

  • #290 c059e8c Thanks @renovate! - fix(deps): update dependency @next/eslint-plugin-next to v16.0.3

  • #302 832e26a Thanks @renovate! - fix(deps): update dependency @next/eslint-plugin-next to v16.0.4

  • #305 fe7b47c Thanks @renovate! - fix(deps): update dependency @next/eslint-plugin-next to v16.0.5

  • #308 a01b656 Thanks @TheCodeDestroyer! - fix: Remove package entry points that point to files the build does not create

    • eslint-config-next and eslint-config-a11y: remove the ./rule-overrides export. These packages have no rules file, so the import always failed.
    • Presets: remove the require export and point main to the ESM file. The build makes ESM only, so the .cjs file never existed.
    • tsup-config: point main to the ESM file for the same reason.

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Minor Changes

  • #308 0c1a5f2 Thanks @TheCodeDestroyer! - feat!: Move all ESLint configs and presets to ESLint 10
    • The eslint peer range is now ^10.0.0. ESLint 9 is no longer supported.
    • Dependency updates: @eslint/js 10.0.1, @eslint/compat 2.1.1, typescript-eslint 8.70.0, eslint-plugin-import-x 4.17.1, eslint-import-resolver-typescript 4.4.5, eslint-plugin-react-hooks 7.1.1, globals 17.12.0.
    • eslint-plugin-react and eslint-plugin-jsx-a11y have no ESLint 10 release yet. The react config now wraps eslint-plugin-react with fixupConfigRules from @eslint/compat. eslint-plugin-jsx-a11y runs on ESLint 10 as is. Your package manager can warn about their eslint peer range. The react/a11y config and preset READMEs show how to hide this warning in pnpm.
    • radix: ESLint 10 ignores the as-needed option, so the rule now always requires a radix. parseInt('10') is now an error. Use parseInt('10', 10).
    • @typescript-eslint/no-loop-func is deprecated. The ts config now uses the core no-loop-func rule from the base config.
    • eslint-plugin-react-hooks 7.1.1 can change results for the React Compiler rules (set-state-in-effect, refs, immutability, preserve-manual-memoization, use-memo).
    • ESLint 10 can report new max-nested-callbacks errors, and typescript-eslint 8.70 can report new no-unnecessary-type-assertion errors.

Patch Changes

@tcd-devkit/[email protected]

Patch Changes

@tcd-devkit/[email protected]

Patch Changes

@tcd-devkit/[email protected]

Patch Changes

@tcd-devkit/[email protected]

Patch Changes

@tcd-devkit/[email protected]

Patch Changes

  • #289 85e7fb9 Thanks @renovate! - chore(deps): update dependency tsup to v8.5.1

  • #308 a01b656 Thanks @TheCodeDestroyer! - fix: Remove package entry points that point to files the build does not create

    • eslint-config-next and eslint-config-a11y: remove the ./rule-overrides export. These packages have no rules file, so the import always failed.
    • Presets: remove the require export and point main to the ESM file. The build makes ESM only, so the .cjs file never existed.
    • tsup-config: point main to the ESM file for the same reason.

@tcd-devkit/[email protected]

Patch Changes

@coderabbitai

coderabbitai Bot commented Nov 14, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 10 times, most recently from 4df49a6 to cb923af Compare November 20, 2025 20:57
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 7 times, most recently from 6d17276 to 18894c5 Compare November 28, 2025 17:38
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 18894c5 to af760f7 Compare November 30, 2025 04:38
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from af760f7 to 64ccfea Compare May 21, 2026 11:33
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 64ccfea to ac0e406 Compare June 13, 2026 08:27
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 8dcb800 to 3a3a9d7 Compare September 22, 2026 20:07
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3a3a9d7 to f0417fa Compare September 22, 2026 20:08
@TheCodeDestroyer
TheCodeDestroyer merged commit 03ba05c into main Sep 22, 2026
1 check passed
@TheCodeDestroyer
TheCodeDestroyer deleted the changeset-release/main branch September 22, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

See More

Successfully merging this pull request may close these issues.

1 participant

@TheCodeDestroyer