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.

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

upgraded jsdom to v26 #2594

Closed

Conversation

coderboy-yash
Copy link

@coderboy-yash coderboy-yash commented Jan 18, 2025

Which problem is this PR solving?

-resolves #2585

Description of the changes

  • this pr has upgraded jsdom version to 26

How was this change tested?

  • npm run test
  • npm run start (compared the jaeger-ui 1.65.0 with this PR changes)

Checklist

@coderboy-yash coderboy-yash requested a review from a team as a code owner January 18, 2025 07:27
@coderboy-yash coderboy-yash requested review from jkowall and removed request for a team January 18, 2025 07:27
@coderboy-yash
Copy link
Author

this is my first pr to jaeger, tell me If there are any problems to this I will try to solve it as soon as possible.

Signed-off-by: coderboy-yash <[email protected]>
@coderboy-yash
Copy link
Author

coderboy-yash commented Jan 18, 2025

@jkowall @yurishkuro please review my pr

@@ -22,7 +22,7 @@
"eslint-plugin-jsx-a11y": "^6.8.0",
"eslint-plugin-react": "7.37.1",
"husky": "9.1.0",
"jsdom": "25.0.1",
"jsdom": "^26.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how is this different from automated PR #2584 which does not pass CI?

@yurishkuro
Copy link
Member

this just replicates the automated PR #2584 which is already known to fail. Closing to reduce noise.

@yurishkuro yurishkuro closed this Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Deps] Upgrade jsdom
3 participants