Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

meta: Update CHANGELOG for 8.21.0 #13110

Merged
merged 9 commits into from
Jul 30, 2024
Merged

meta: Update CHANGELOG for 8.21.0 #13110

merged 9 commits into from
Jul 30, 2024

Commits on Jul 30, 2024

  1. feat(solidstart): Add server action instrumentation helper (#13035) 

    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' })
    })
}
```
    @andreiborza
    andreiborza authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    71af30f View commit details
    Browse the repository at this point in the history

  2. test(astro): Switch to explicit vitest imports (#13093) 

    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.
    @AbhiPrasad
    AbhiPrasad authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    b7e62c4 View commit details
    Browse the repository at this point in the history

  3. feat(nestjs): Automatic instrumentation of nestjs middleware (#13065) 

    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.
    @nicohrubec
    nicohrubec authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    e3af1ce View commit details
    Browse the repository at this point in the history

  4. Merge branch 'develop' into lms/sync-master-develop

    @Lms24
    Lms24 committed Jul 30, 2024
    Configuration menu
    Copy the full SHA
    cfafa71 View commit details
    Browse the repository at this point in the history

  5. fix(nextjs): Only delete clientside bundle source maps with `sourcema… 

    …ps.deleteFilesAfterUpload` (#13102)
    @lforst
    lforst authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    ce53667 View commit details
    Browse the repository at this point in the history

  6. Merge pull request #13109 from getsentry/lms/sync-master-develop 

    misc: Sync master -> develop
    @Lms24
    Lms24 authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    d222dd5 View commit details
    Browse the repository at this point in the history

  7. fix(browser-integration-tests): Fix feedback addon CDN bundle integra… 

    …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
    @Lms24
    Lms24 authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    d73a567 View commit details
    Browse the repository at this point in the history

  8. feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107) 

    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.
    @AbhiPrasad
    AbhiPrasad authored Jul 30, 2024
    Configuration menu
    Copy the full SHA
    51f85e6 View commit details
    Browse the repository at this point in the history

  9. meta: Update CHANGELOG for 8.21.0

    @Lms24
    Lms24 committed Jul 30, 2024
    Configuration menu
    Copy the full SHA
    f3a4109 View commit details
    Browse the repository at this point in the history