chore: release main #6107
Merged
chore: release main #6107
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
netlify-circleci
force-pushed
the
release-please--branches--main
branch
3 times, most recently
from
1f040d3 to
9394055
Compare
netlify-circleci
force-pushed
the
release-please--branches--main
branch
from
87c5320 to
7cb8d19
Compare
mrstork
approved these changes
Mar 12, 2025
serhalp
added a commit
that referenced
this pull request
Mar 17, 2025
`@netlify/build` and `@netlify/config` had dev dependencies on the local `@netlify/testing` package (which is a local package only, not published to NPM) but they weren't specified in its `package.json` So: - These imports only sort of happened to work - TS wasn't complaining because we've explictly remapped that import: https://github.com/netlify/build/blob/65206cf/tsconfig.base.json#L30. - ESLint wasn't complaining because although we are using eslint-plugin-import, we aren't using the recommended ruleset and we aren't enabling [`no-extraneous-dependencies`] (https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules) - release-please didn't know about that part of our dependency graph, so it was opening [release PRs like this one](#6107) that should have bumped `@netlify/build` and `@netlify/config` in `packages/testing` but [did not](#6124) pnpm and yarn support `workspace:*` to make this local dependency explicit, but we're using npm workspaces, which do not. I opted to include a `-local` prefix to make this extra explicit.
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
🤖 I have created a release beep boop
build: 30.0.0
30.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Features
Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)Dependencies
build-info: 9.0.0
9.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)config: 21.0.0
21.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)Dependencies
functions-utils: 5.3.9
5.3.9 (2025-03-12)
Dependencies
headers-parser: 8.0.0
8.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)nock-udp: 4.0.0
4.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)zip-it-and-ship-it: 10.0.0
10.0.0 (2025-03-12)
⚠ BREAKING CHANGES
@netlify/headers-parsertypes (#6104)Features
Bug Fixes
@netlify/headers-parsertypes (#6104) (bc5e35a)This PR was generated with Release Please. See documentation.