build(deps): bump json5 from 1.0.1 to 1.0.2

[dependabot]

Bumps json5 from 1.0.1 to 1.0.2.

Release notes

Sourced from json5's releases.

v1.0.2

• Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295). This has been backported to v1. (#298)

Changelog

Sourced from json5's changelog.

Unreleased [code, diff]

v2.2.3 [code, diff]

• Fix: json5@2.2.3 is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2 [code, diff]

• Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

• Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0 [code, diff]

• New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

• Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2 [code, diff]

... (truncated)

Commits

• a62db1e 1.0.2
• e0c23fe docs: update CHANGELOG for v1.0.2
• 62a6540 fix: add proto to objects and arrays
• See full diff 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 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.

[ghost]

I'd help to merge this change, however I find myself not authorized....
Can anyone help to give the authentication to me?

[Trott]

I'd help to merge this change, however I find myself not authorized.... Can anyone help to give the authentication to me?

As a member of @nodejs/website, you should be able to merge it. @ovflowd Did you do something to make a content freeze while you do the Next.js implementation or something like that?

[ovflowd]

As a member of @nodejs/website, you should be able to merge it. @ovflowd Did you do something to make a content freeze while you do the Next.js implementation or something like that?

Nope, I only increase the required amount of approvals to two, nothing else 🤔

[Trott]

Nope, I only increase the required amount of approvals to two, nothing else 🤔

If you haven't already, we should check with @nodejs/releasers that that won't be a problem for them when publishing release blogs and things like that. If it is, we can maybe make the team maintainers or admins so they can bypass the requirement. (Or maybe that only applies to org owners? 5 of the 9 members of that team are already org owners, so it may not be a problem.)

[ovflowd]

GitHub allows you to choose teams to bypass the rules, so we can just ad the releasers to that.

By default only org owners and repository admins can bypass these rules.

[ghost]

Maybe we can discuss here: https://github.com/nodejs/nodejs.org/discussions/5002. I created a new one.