-
-
Notifications
You must be signed in to change notification settings - Fork 18
chore: Upgrade sentry/node to latest #627
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.
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
Merged
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
ee47e01 to
45490e5
Compare
hubertdeng123
approved these changes
Nov 24, 2025
BYK
added a commit
that referenced
this pull request
Nov 24, 2025
* chore: Upgrade sentry/node to latest * fix
BYK
added a commit
that referenced
this pull request
Nov 24, 2025
* Refactor changelog generation to use release.yml for categorization Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Fix: Handle ENOENT error and improve changelog generation Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor: Improve changelog generation tests Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Fix failing tests (#625) * Refactor: Improve changelog generation and mock fs This commit refactors the changelog generation logic to correctly handle category-level exclusions and improves the mocking of the `fs` module by using `jest.requireActual` for `readFileSync`. It also updates the `gcsAPI` tests to use the mocked `fs.existsSync`. Co-authored-by: burak.kaya <burak.kaya@sentry.io> * chore: Remove package-lock.json and regenerate yarn.lock - Remove npm-generated package-lock.json file - Regenerate yarn.lock with current dependencies - Project uses yarn as the package manager * fix: Resolve all TypeScript compilation and test failures Fixed multiple TypeScript compilation errors and dependency issues: **TypeScript Fixes:** - Fixed github.ts: Changed Promise resolve callback to match expected signature - Fixed awsLambdaLayerManager.ts: - Added Runtime import and cast CompatibleRuntimes to Runtime[] - Cast headers to Record<string, string> for fetch compatibility - Fixed registry.ts: Added explicit RemoteArtifact type to mapLimit callback - Fixed brew.ts: Added RemoteArtifact import and type annotation **Configuration Fixes:** - tsconfig.build.json: Added noImplicitUseStrict: false to override deprecated parent config option - jest.config.js: Added transformIgnorePatterns for ESM modules (dot-prop, configstore) - package.json: Pinned dot-prop to ^5.3.0 to avoid ESM-only version 10.x that breaks Jest **Test Results:** - All 38 test suites passing ✅ - 369 tests passing, 1 skipped (370 total) - 28 snapshots passing --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> * Refactor changelog generation to use GitHub PR format Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor changelog generation to use Sets for exclusions Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor: Normalize release config exclusions to use empty sets Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor: Simplify changelog normalization and matching logic Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor: Simplify changelog exclusion logic and update yarn.lock This commit refactors the changelog exclusion logic to be more concise and removes unnecessary checks. It also updates the yarn.lock file to reflect the latest dependency versions. Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Checkpoint before follow-up message Co-authored-by: burak.kaya <burak.kaya@sentry.io> * Refactor changelog generation and update tsconfig Co-authored-by: burak.kaya <burak.kaya@sentry.io> * build(deps-dev): bump js-yaml from 4.1.0 to 4.1.1 (#624) Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.1.0...4.1.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.1.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * build(deps): bump js-yaml from 3.13.1 to 4.1.1 (#626) Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.13.1 to 4.1.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.13.1...4.1.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.1.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore: Upgrade sentry/node to latest (#627) * chore: Upgrade sentry/node to latest * fix * fix: Upgrade Jest to 29.7.0 to fix ESM/CJS compatibility with Node 22 The older Jest version had issues with strip-ansi ESM module resolution when running on Node.js 22. Also added a resolution to pin strip-ansi in @jest/reporters to the CJS-compatible version. * fix: Remove corrupted 'yarn' prefix from test file Rebase artifact left 'yarn' prefix on a line in the test file. * fix: Replace Set.intersection() with loop for Node 20 compatibility Set.intersection() is only available in Node 22+. Use a loop to check for excluded labels instead. * fix: Strip redundant PR number suffix from PR titles in changelog When formatting PR entries for the changelog, the PR number like '(#123)' at the end of the title is now stripped since the PR link is already included at the end of the entry. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
No description provided.