meta: Update CHANGELOG for 8.21.0 by Lms24 · Pull Request #13110 · getsentry/sentry-javascript

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

Lms24 · 2024-07-30T15:00:53Z

Second try! This PR just updates the already existing 8.21.0 entry from a previous release attempt. This didn't work but we could retract everything in time and didn't publish anything yet. So starting the release under the same version should work 🤞

Can be used like this: ```js const getUserData = async () => { 'use server'; return await withServerActionInstrumentation('getData', () => { return { prefecture: 'Kanagawa' }; }); }; ``` Can also be used for api routes like this: ```js export async function GET() { return await withServerActionInstrumentation('getUser', () => { return json({ prefecture: 'Akita' }) }) } ```

As per https://vitest.dev/config/#globals > By default, vitest does not provide global APIs for explicitness I think we should follow vitest defaults here and explicitly import in the APIs that we need. This refactors our Astro SDK tests to do so. I also went ahead and fixed up some TS errors in some tests. This change also removes `environment: 'jsdom'` from the vite config as it seems nothing needs this for astro. This should means that our tests are not polluted with jsdom globals, and that future writers have to explicitly opt-in to the behaviour.

Adds middleware instrumentation to the `@sentry/nestjs`. The implementation lives in `@sentry/node` so that both users using `@sentry/nestjs` directly as well as users still on `@sentry/node` benefit. The instrumentation is automatic without requiring any additional setup. The idea is to hook into the Injectable decorator (every class middleware is annotated with `@Injectable` and patch the `use` method if it is implemented. Caveat: This implementation only works for class middleware, which implements the `use` method, which seems to be the standard for implementing middleware in nest. However, nest also provides functional middleware, for which this implementation does not work.

…ps.deleteFilesAfterUpload` (#13102)

misc: Sync master -> develop

…tion test setup (#13108) - Add symlinks to lazy-loaded feedback sub-integrations whenever we discover that `feedbackIntegration` is imported in a test app - Stop forwarding the CDN bundle request to the actual CDN but throw a hard error instead

ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

andreiborzaand others added 9 commits July 30, 2024 14:56

Merge branch 'develop' into lms/sync-master-develop
cfafa71

fix(nextjs): Only delete clientside bundle source maps with `sourcema…
ce53667
…ps.deleteFilesAfterUpload` (#13102)

Merge pull request#13109from getsentry/lms/sync-master-develop
d222dd5
misc: Sync master -> develop

feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
51f85e6
ref https://github.com/nodejs/import-in-the-middle/releases/tag/import-in-the-middle-v1.11.0 Bumping this for the bug fix, we can expose the `registerOptions` in another PR.

meta: Update CHANGELOG for 8.21.0
f3a4109

Lms24 requested review from a team, lforst and s1gr1d and removed request for a teamJuly 30, 2024 15:02

Lms24 self-assigned this Jul 30, 2024

AbhiPrasad approved these changes Jul 30, 2024
View reviewed changes

Lms24 changed the base branch from develop to masterJuly 30, 2024 15:13

Lms24 merged commit dd3b1aa into masterJul 30, 2024

Lms24 deleted the prepare-release/8.21.0 branch July 30, 2024 15:14

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Uh oh!

Conversation

Lms24 commented Jul 30, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading

Lms24 commented Jul 30, 2024•
edited
Loading