fix: update semantic-release config so new v29 major is marked as latest on npm
#1772
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions bot
pushed a commit
that referenced
this pull request
Jun 18, 2025
# [29.0.0](v28.14.0...v29.0.0) (2025-06-18) ### Bug Fixes * remove `jest/no-alias-methods` from `styles` config ([df3b8cd](df3b8cd)) * update semantic-release config so new v29 major is marked as latest on `npm` ([#1772](#1772)) ([531c8ba](531c8ba)) ### Features * drop support for `[@typescript-eslint](https://github.com/typescript-eslint)` v6 ([fbf49a0](fbf49a0)) * drop support for `[@typescript-eslint](https://github.com/typescript-eslint)` v7 ([d77ac46](d77ac46)) * drop support for ESLint v7 ([60e26c2](60e26c2)) * drop support for ESLint v8.x prior to v8.57.0 ([854cef4](854cef4)) * drop support for Node v16 ([8000c3d](8000c3d)) * drop support for Node v18 ([f442a2a](f442a2a)) * drop support for Node v20.x prior to v20.12.0 ([83c130b](83c130b)) * drop support for Node v21 ([e6d5a25](e6d5a25)) * drop support for Node v23 ([d7fe2d4](d7fe2d4)) * **unbound-method:** remove `docs.recommended` and `docs.requiresTypeChecking` properties ([1d53075](1d53075)) ### BREAKING CHANGES * dropped support for ESLint v8.x prior to v8.57.0 * dropped support for Node v20.x prior to v20.12.0 * dropped support for Node v23 * dropped support for Node v18 * **unbound-method:** removed `docs.recommend` and `docs.requiresTypeChecking` from `unbound-method` * dropped support for `@typescript-eslint` v7 * dropped support for `@typescript-eslint` v6 * `jest/no-alias-methods` has been removed from the `styles` config as its already in the `recommended` config * dropped support for ESLint v7 * dropped support for Node v21 * dropped support for Node v16
github-actions bot
pushed a commit
that referenced
this pull request
Jun 18, 2025
# [29.0.0](v28.14.0...v29.0.0) (2025-06-18) ### Bug Fixes * remove `jest/no-alias-methods` from `styles` config ([df3b8cd](df3b8cd)) * update semantic-release config so new v29 major is marked as latest on `npm` ([#1772](#1772)) ([531c8ba](531c8ba)) ### Features * drop support for `[@typescript-eslint](https://github.com/typescript-eslint)` v6 ([fbf49a0](fbf49a0)) * drop support for `[@typescript-eslint](https://github.com/typescript-eslint)` v7 ([d77ac46](d77ac46)) * drop support for ESLint v7 ([60e26c2](60e26c2)) * drop support for ESLint v8.x prior to v8.57.0 ([854cef4](854cef4)) * drop support for Node v16 ([8000c3d](8000c3d)) * drop support for Node v18 ([f442a2a](f442a2a)) * drop support for Node v20.x prior to v20.12.0 ([83c130b](83c130b)) * drop support for Node v21 ([e6d5a25](e6d5a25)) * drop support for Node v23 ([d7fe2d4](d7fe2d4)) * **unbound-method:** remove `docs.recommended` and `docs.requiresTypeChecking` properties ([1d53075](1d53075)) ### BREAKING CHANGES * dropped support for ESLint v8.x prior to v8.57.0 * dropped support for Node v20.x prior to v20.12.0 * dropped support for Node v23 * dropped support for Node v18 * **unbound-method:** removed `docs.recommend` and `docs.requiresTypeChecking` from `unbound-method` * dropped support for `@typescript-eslint` v7 * dropped support for `@typescript-eslint` v6 * `jest/no-alias-methods` has been removed from the `styles` config as its already in the `recommended` config * dropped support for ESLint v7 * dropped support for Node v21 * dropped support for Node v16
github-actions bot
pushed a commit
that referenced
this pull request
Jun 18, 2025
## [29.0.1](v29.0.0...v29.0.1) (2025-06-18) ### Bug Fixes * update semantic-release config so new v29 major is marked as latest on `npm` ([#1772](#1772)) ([531c8ba](531c8ba))
|
🎉 This PR is included in version 29.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts #1585 which'll hopefully mean next time
semantic-releasewill prefix the version with-next- I'm landing it as afixso that it'll end up marking a v29.x.x version as the latest onnpm