meta(changelog): Update changelog for 10.32.1 #18578
Merged
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
chore(ci): Skip build job when no code changes present
[Gitflow] Merge master into develop
If the error is caught with the hono error handler, no `trace` data was sent alongside the event. This PR fixed this. Before: <img width="216" height="80" alt="image" src="https://github.com/user-attachments/assets/35bc99b7-4a59-40e3-aad8-10130f816d68" /> After: <img width="248" height="85" alt="image" src="https://github.com/user-attachments/assets/dbc89577-0832-4166-8532-5210dc5e5d99" />
This removes a test that only asserted on successful deployment of a static cloudflare app. No actual tests. I don't think there's much value in this but it required a repo-specific env secret we can now get rid of. (fwiw, long-term we definitely want cloudflare-deployed e2e tests but we'll likely need a better test setup anyway) Closes #18568 (added automatically)
Explicitly enable `any` usage in typescript in: - `dev-packages`, since those are largely integration and E2E tests. (This is done with the addition of a `dev-packages/.eslintrc.js` file.) - `packages/*/test/`, since those are all tests. (This is done with a rule override added to the root `.eslintrc.js` file.) - Several one-off allowances, generally for vendored types from third party sources, and cases involving function type extension/overriding that TypeScript can't follow. (These are done with file/line overrides, explicit `as` casting, and adding type inference to the `isInstanceOf` method.) In other places (ie, in exported production code paths), replace `any` with `unknown`, and upgrade the `@typescript/no-explicit-any` lint rule to an error. This silences a lot of eslint warnings that were habitually ignored, and encourages us to not opt out of strict type safety in our exported code.
Makes sure that `gen_ai.input_tokens` value contains `gen_ai.input_tokens.cached`
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
Comment on lines
+13
to
23
| <details> | ||
| <summary> <strong>Internal Changes</strong> </summary> | ||
|
|
||
| - chore(lint): prefer 'unknown' to 'any', fix lint warnings | ||
| - chore(test): Remove `cloudflare-astro` e2e test ([#18567](https://github.com/getsentry/sentry-javascript/pull/18567)) | ||
|
|
||
| </details> | ||
|
|
||
| ## 10.32.0 | ||
|
|
||
| ### Important Changes |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
andreiborza
changed the title
10.32.1
nicohrubec
approved these changes
Dec 19, 2025
Lms24
force-pushed
the
prepare-release/10.32.1
branch
from
a984f91 to
a981a3d
Compare
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
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.
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint) & (yarn test).Closes #issue_link_here