Bump nanoid and @redocly/realm

[dependabot]

Bumps nanoid to 5.0.9 and updates ancestor dependency @redocly/realm. These dependencies need to be updated together.

Updates nanoid from 3.3.7 to 5.0.9

Release notes

Sourced from nanoid's releases.

5.0.9

• Fixed a way to break Nano ID by passing non-integer size (by @​myndzi).

5.0.8

• Reduced customAlphabet size (by @​kirillgroshkov).

5.0.7

• Fixed Parcel support (by @​WilhelmYakunin).

5.0.6

• Fixed React Native support.

Changelog

Sourced from nanoid's changelog.

5.0.9

• Fixed a way to break Nano ID by passing non-integer size (by @​myndzi).

5.0.8

• Reduced customAlphabet size (by @​kirillgroshkov).

5.0.7

• Fixed Parcel support (by @​WilhelmYakunin).

5.0.6

• Fixed React Native support.

5.0.5

• Make browser’s version faster by increasing size a little (by Samuel Elgozi).

5.0.4

• Fixed CLI docs (by @​ilyaboka).

5.0.3

• Fixed CLI docs (by Chris Schmich).

5.0.2

• Fixed webcrypto import (by Divyansh Singh).

5.0.1

• Fixed Node.js 18 support.

5.0

• Moved Node.js version to Web Crypto API.
• Removed async API since Web Crypto API has only sync version.
• Removed Node.js 14 and 16 support.

4.0.2

• Added link to Github Sponsors.

4.0.1

• Reduced npm package size (by @​HiChen404).

4.0

• Removed CommonJS support. Nano ID 4 will work only with ESM applications. We will support 3.x branch with CommonJS for users who can’t migrate to ESM.
• Removed Node.js 10 and Node.js 12 support.
• Reduced npm package size.

3.3.8

• Fixed a way to break Nano ID by passing non-integer size (by @​myndzi).

Commits

• 65a38ac Release 5.0.9 version
• b00d120 Merge after 3.3.8 release
• 3044cd5 Release 3.3.8 version
• cdc3edc Update size limit
• 4fe3495 Update size limit
• d643045 Fix pool pollution, infinite loop (#510)
• 0daa00f Additional fixes and tests for #508 (#509)
• 313a14e Update dependencies
• eb2db95 Fix size limit and linting
• 9da8f60 Fix pool pollution, infinite loop (#508)
• Additional commits viewable in compare view

Updates @redocly/realm from 0.103.1 to 0.114.1

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@redocly/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+518	175 MB	marshevskyy
npm/[email protected]	None	0	11 kB	ai
npm/[email protected]	None	0	22.7 MB	andrewbranch, minestarks, rbuckton, ...5 more

🚮 Removed packages: npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@jridgewell/[email protected], npm/@redocly/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: emoji-regex~~-xs~~	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[mDuo13]

Superseded by #2945

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.