chore(deps): bump @redocly/cli from 1.34.5 to 2.0.2 in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: @redocly/cli.

Updates @redocly/cli from 1.34.5 to 2.0.2

Release notes

Sourced from @​redocly/cli's releases.

@​redocly/cli@​2.0.2

Patch Changes

• Made executionTimeout parameter optional in the run function exported from respect-core.
• Updated @​redocly/respect-core to v2.0.2.

@​redocly/cli@​2.0.1

Patch Changes

• Fixed an issue where the no-required-schema-properties-undefined rule incorrectly resolved nested $refs relative to the file in which they were defined.
• Fixed an issue where multipart form-data parameters were not properly resolved and evaluated before sending requests.
• Updated @​redocly/openapi-core to v2.0.1.

@​redocly/cli@​2.0.0

Major Changes

• Removed backward compatibility for the spec rule. Use struct instead.
• Removed support for the deprecated apiDefinitions option in the Redocly config. Use apis instead. Removed the labels field within the apis section, which was associated with the legacy Redocly API Registry product.
• Removed support for default config file names other than redocly.yaml.
• Removed support for the deprecated features.openapi and features.mockServer configuration options. Use openapi and mockServer directly instead.
• Removed backward compatibility for the deprecated lint and styleguide options in the Redocly config. Use rules, decorators and other related options on the root level instead.
• Removed the deprecated disallowAdditionalProperties option support in rules. Use allowAdditionalProperties instead.
• Removed support for the deprecated theme property of Redocly config. All the properties of theme are now available in the config root.
• Removed the deprecated path-excludes-patterns and info-license-url rules.
• Removed the deprecated undefined assertion. Use defined instead.
• Removed support for the legacy Redocly API Registry in favor of the new Reunite platform. Reunite provides improved API management capabilities and better integration with Redocly's tooling ecosystem. Migrated the login and push commands to work exclusively with Reunite. Removed the preview-docs command as part of platform modernization. Use the preview command instead.
• Removed support for the deprecated referenceDocs option, which was related to the legacy Reference docs product.
• Removed support for the deprecated assert/ prefix in configurable rules. Use rule/ prefix instead.
• Migrated the codebase to ES Modules from CommonJS, bringing improved code organization and better support for modern JavaScript features. Update to Node.js version 20.19.0+, 22.12.0+, or 23+.

Minor Changes

• Added x-security extension for Respect that enables secure handling of authentication in Arazzo workflows. Use this extension to:

  • Define security schemes at the step level using either predefined schemes or inline definitions
  • Pass values of secrets (passwords, tokens, API keys)
  • Support multiple authentication types including API Key (query, header, or cookie), Basic Authentication, Bearer Token, Digest Authentication, OAuth2, and OpenID Connect
  • Automatically transform security parameters into appropriate HTTP headers or query parameters

• Added environment variable support for CLI arguments using Yargs .env() method to parse environment variables with matching prefixes.

... (truncated)

Commits

• e9bdae8 chore: 🔖 release new versions (#2234)
• b2fdf87 docs: update the v2 migration guide (#2231)
• 48665ab feat: made executionTimeout optional for exported respect-core run (#2233)
• f119dc5 chore: 🔖 release new versions (#2227)
• fc3ff08 fix: respect multipart form-data resolution (#2229)
• 1d4feef hotfix: improve the no-required-schema-properties-undefined rule ref resolver...
• 2205712 fix: resolve nested shemas relative to the file in the no-required-schema-pro...
• 6e7e2ae docs: fix the info-license-strict slug (#2223)
• 7c588a8 docs: add missing slugs to respect-related commands (#2222)
• cf94964 docs: make v2 the current version (#2220)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[cursor]

Bug: Node.js Version Conflict with Dependency

Node.js version incompatibility: The project's package.json declares Node.js support >=18.0.0 in its engines field. However, the upgraded @redocly/[email protected] dependency requires Node.js ">=22.12.0 || >=20.19.0 <21.0.0". This causes installation or runtime failures for users on Node.js 18.x, 19.x, and 20.0.0-20.18.x, as these versions are incompatible with the dependency.

package.json#L79-L80

apify-docs/package.json

Lines 79 to 80 in c9635c2

	"@mdx-js/react": "^3.0.1",
	"@redocly/cli": "^2.0.2",

package.json#L93-L100

apify-docs/package.json

Lines 93 to 100 in c9635c2

	"raw-loader": "^4.0.2",
	"react": "^19.1.0",
	"react-dom": "^19.1.0",
	"react-github-btn": "^1.4.0",
	"search-insights": "2.17.3",
	"styled-components": "6.1.19",
	"unist-util-visit": "^5.0.0"
	},

---

Comment bugbot run to trigger another review on this PR

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml