Skip to content

[8.18] Upgrade prismjs 1.29.0 → 1.30.0 (#222019)#222418

Merged
jeramysoucy merged 3 commits intoelastic:8.18from
jeramysoucy:backport/8.18/pr-222019
Jun 4, 2025
Merged

[8.18] Upgrade prismjs 1.29.0 → 1.30.0 (#222019)#222418
jeramysoucy merged 3 commits intoelastic:8.18from
jeramysoucy:backport/8.18/pr-222019

Conversation

@jeramysoucy
Copy link
Contributor

Backport

This will backport the following commits from main to 8.18:

Questions ?

Please refer to the Backport tool documentation

## Summary

Upgrades the `prismjs` dependency to version 1.30.0 where possible.

(cherry picked from commit 6968240)

# Conflicts:
#	yarn.lock
@jeramysoucy jeramysoucy added the backport This PR is a backport of another PR label Jun 3, 2025
@jeramysoucy jeramysoucy enabled auto-merge (squash) June 3, 2025 16:26
@jeramysoucy jeramysoucy requested a review from a team June 4, 2025 07:53
Copy link
Contributor

@SiddharthMantri SiddharthMantri left a comment

Choose a reason for hiding this comment

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

One non-blocking question. Looks good otherwise

integrity sha512-DEvV2ZF2r2/63V+tK8hQvrR2ZGn10srHbXviTlcv7Kpzw8jWiNTqbVgjO3IY8RxrrOUF8VPMQQFysYYYv0YZxw==

prismjs@~1.27.0:
version "1.27.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Question: I wonder why the next line for the registry is yarnpkg here vs npmjs in the root PR: https://github.com/elastic/kibana/pull/222019/files#diff-51e4f558fae534656963876761c95b83b6ef5da5103c4adef6768219ed76c2deR26402

Doesn't seem like an issue but just wanted to highlight

@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 4, 2025

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #65 / APM API tests settings/anomaly_detection/update_to_v3.spec.ts trial no archive Updating ML jobs to v3 when there are only v2 jobs "after all" hook for "creates a new job for each environment that has a v2 job"
  • [job] [logs] FTR Configs #65 / APM API tests settings/anomaly_detection/update_to_v3.spec.ts trial no archive Updating ML jobs to v3 when there are only v2 jobs "after all" hook for "creates a new job for each environment that has a v2 job"

Metrics [docs]

✅ unchanged

History

@jeramysoucy jeramysoucy merged commit 52f83ad into elastic:8.18 Jun 4, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants