chore: bump update-notifier

[layershifter]

Motivation

An attempt to bump update-notifier (similar to #7684).

The fix for imports arrived in Yarn 3.2.4 (yarnpkg/berry#4862), that was a blocker before #7684 (comment).

# yarn -v
3.4.1

# yarn config get nodeLinker 
pnp

# yarn node     
Welcome to Node.js v16.14.0.
Type ".help" for more information.
> (await import('chalk')).colors
[
  'black',           'red',            'green',
  'yellow',          'blue',           'magenta',
  'cyan',            'white',          'blackBright',
  'gray',            'grey',           'redBright',
  'greenBright',     'yellowBright',   'blueBright',
  'magentaBright',   'cyanBright',     'whiteBright',
  'bgBlack',         'bgRed',          'bgGreen',
  'bgYellow',        'bgBlue',         'bgMagenta',
  'bgCyan',          'bgWhite',        'bgBlackBright',
  'bgGray',          'bgGrey',         'bgRedBright',
  'bgGreenBright',   'bgYellowBright', 'bgBlueBright',
  'bgMagentaBright', 'bgCyanBright',   'bgWhiteBright'
]

Related issues/PRs

Fixes #8277.

[facebook-github-bot]

Hi @layershifter!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	53b8e9c
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/63ee73407248ca00088d72f3
😎 Deploy Preview	https://deploy-preview-8660--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 85	🟢 97	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 83	🟢 100	🟢 100	🟢 100	🟢 90	Report

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[Josh-Cena]

Could you commit the lockfile changes?

[layershifter]

Could you commit the lockfile changes?

@Josh-Cena Oops, sorry missed that. As I see @slorber have already done that.

[xnivaxhzne]

@slorber may I know when this change will get released? Asking because some changes merged before the date on which the current PR got merged were went in the release 2.4.0. I couldn't understand the release process.

[slorber]

@kavinkuma6 all PRs target the upcoming v3 by default, unless we backport them to the v2 branch (and this one has not been backported)

You can use a canary release if you need this feature right now

[xnivaxhzne]

@kavinkuma6 all PRs target the upcoming v3 by default, unless we backport them to the v2 branch (and this one has not been backported)

You can use a canary release if you need this feature right now

Got it man. Thanks