fix(deps): update dependency atom-package-deps to v8

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
atom-package-deps (source)	5.1.0 -> 8.0.0

---

Release Notes

steelbrain/package-deps (atom-package-deps)

v8.0.0

Compare Source

• Potentially unstable: Minify the output to reduce size to ~10kb from ~30kb. (Thanks @​aminya)

Although none of the APIs have changed, this change may be potentially unstable, so marking it as semver-major so consumers have to opt-in to this.

v7.2.3

Compare Source

v7.2.2

Compare Source

• Another attempt to fix Windows usages - #​332 (Thanks @​UziTech)

v7.2.1

Compare Source

• Fix compatibility with Windows usernames with spaces - #​331 (Thanks @​deankevorkian)

v7.2.0

Compare Source

• Add Typescript definitions
• Fix installing dependencies in CI on Windows
• Allow purely string entries for name in dependencies

v7.1.0

Compare Source

• Readd ability to hide user prompt

v7.0.3

Compare Source

• Fix support for notifications-plus package (Thanks @​UziTech)

v7.0.2

Compare Source

• Fix a bug where error would be thrown if user already had one of the packages installed (Thanks @​lierdakil)

v7.0.1

Compare Source

• Fix a dev dependency accidentally slipping into post-install script

v7.0.0

Compare Source

• BREAKING Change function signature to get rid of promptUser
• BREAKING Change format of package-deps in manifest from "my-name:my-version" to be { "name": "my-name", "minimumVersion": "my-version" }
• BREAKING Instead of accepting a semver-range for version, you can now only specify a minimum version in x.y.z format, instead of for example >=2
• Add support for optional/group packages where users only have to install one of many, and are given a choice at runtime. Signature becomes Dependency[][] instead of Dependency[]
• Add support for using through CLI for CI and similar purposes

v6.0.0

Compare Source

• Fix progress bar on newer Atom versions
• Use rollup to bundle dependencies to decrease load times (Thanks @​aminya)

While there's no API breaking change, the distribution format and internal code has changed signficiantly enough that it MAY have some bugs left despite our testing. Therefore, to not break existing expectations, I (@​steelbrain) am pushing this out as semver-major.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit