Skip to content

chore(cli): update redoc to v2.5.3#2842

Open
tatomyr wants to merge 2 commits into
mainfrom
chore/update-redoc
Open

chore(cli): update redoc to v2.5.3#2842
tatomyr wants to merge 2 commits into
mainfrom
chore/update-redoc

Conversation

@tatomyr
Copy link
Copy Markdown
Collaborator

@tatomyr tatomyr commented May 29, 2026

What/Why/How?

Updated redoc to v2.5.3

Reference

Testing

Screenshots (optional)

Check yourself

  • This PR follows the contributing guide
  • All new/updated code is covered by tests
  • Core code changed? - Tested with other Redocly products (internal contributions only)
  • New package installed? - Tested in different environments (browser/node)
  • Documentation update has been considered

Security

  • The security impact of the change has been considered
  • Code follows company security practices and guidelines

Note

Low Risk
Patch-level dependency bump for the docs renderer only; no CLI command or auth logic changes beyond regenerated HTML fixture URLs.

Overview
Bumps the redoc dependency from 2.5.1 to 2.5.3 in @redocly/cli, with a changeset noting the patch for consumers. package-lock.json is refreshed (including nested redoc deps such as @redocly/openapi-core and openapi-sampler).

E2E and smoke HTML snapshots are updated so embedded docs load redoc.standalone.js from the Redocly CDN at v2.5.3, matching what build-docs emits when it pins the script URL to the installed Redoc version.

Reviewed by Cursor Bugbot for commit 84724b8. Bugbot is set up for automated code reviews on this repo. Configure here.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 29, 2026

🦋 Changeset detected

Latest commit: 84724b8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@redocly/cli Patch
@redocly/openapi-core Patch
@redocly/respect-core Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tatomyr tatomyr self-assigned this May 29, 2026
@tatomyr tatomyr marked this pull request as ready for review May 29, 2026 13:15
@tatomyr tatomyr requested review from a team as code owners May 29, 2026 13:15
@DmitryAnansky DmitryAnansky self-requested a review May 29, 2026 13:16
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 29, 2026

CLI Version Mean Time ± Std Dev (s) Relative Performance (Lower is Faster)
cli-latest 2.022s ± 0.013s ▓ 1.00x (Fastest)
cli-next 2.049s ± 0.020s ▓ 1.01x

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 29, 2026

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 81.06% (🎯 80%) 7303 / 9009
🔵 Statements 80.41% (🎯 80%) 7587 / 9435
🔵 Functions 84.08% (🎯 83%) 1463 / 1740
🔵 Branches 72.55% (🎯 72%) 4939 / 6807
File CoverageNo changed files found.
Generated in workflow #10016 for commit 84724b8 by the Vitest Coverage Report Action

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit df5e688. Configure here.

Comment thread package-lock.json Outdated
"devDependencies": {
"@types/js-levenshtein": "^1.1.0",
"@types/js-yaml": "^4.0.3",
"@types/js-yaml": "^4.0.9",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lockfile out of sync with packages/core/package.json

Medium Severity

The package-lock.json entry for the packages/core workspace now lists "js-yaml": "^4.1.1" and "@types/js-yaml": "^4.0.9", but the actual packages/core/package.json still specifies "js-yaml": "^4.1.0" and "@types/js-yaml": "^4.0.3". This mismatch between the lockfile and the package manifest will cause npm ci to fail since it strictly enforces consistency between these files.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit df5e688. Configure here.

@DmitryAnansky DmitryAnansky self-requested a review May 29, 2026 13:18
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.

3 participants