Bump parse-path and gatsby

[dependabot[bot]]

Bumps parse-path to 7.0.0 and updates ancestor dependency gatsby. These dependencies need to be updated together.

Updates parse-path from 4.0.2 to 7.0.0

Release notes

Sourced from parse-path's releases.

7.0.0

Add the parse_failed property — whether the input was parsed successfully or not.

6.0.0

parse-path 6.0.0

Breaking changes

• The resource property will not contain the port anymore. Added the host property which has the port too.

5.0.0

parse-path 5.0.0

:star: This is a major release of parse-path! :star:

Breaking changes

• parse-path will not parse git@... ssh URLs anymore. Use parse-url for that.
• If the input url has a trailing slash, the trailing slash will be added in the pathname too.
• The port field is a string. By default empty.
• Added the password field (default: "")
• The resource may contain the port in it (e.g. resource: "domain.com:4200").

Features

• Faster
• More secure
• Cleaner codebase

Any questions, suggestions, contributions are always welcome! :blush:

4.0.4

Remove the new line characters.

4.0.3

Handle backslash in the input and use query-string, so the module is supported in the browser

Commits

• c53b17e Updated docs
• a0269b1 :arrow_up: 7.0.0 :tada:
• e3ee527 :arrow_up: 6.1.0 :tada:
• 4bae19e Add the parse_failed property.
• 3d1525d Updated docs
• 31f7a33 Add the host property
• 02995c6 Merge branch 'patch-1' of github.com:viceice/parse-path into new-version
• cbb46e0 :arrow_up: 6.0.0 :tada:
• 01b23dc test: add test
• 9032ebb fix: use hostname instead of host
• Additional commits viewable in compare view

Updates gatsby from 2.25.0 to 4.24.6

Release notes

Sourced from gatsby's releases.

v4.24

Welcome to gatsby@4.24.0 release (September 2022 #2)

Key highlights of this release:

• Gatsby 5 Alpha
• Updating File System Routes on data changes

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.23

Welcome to gatsby@4.23.0 release (September 2022 #1)

Key highlights of this release:

• Open RFCs

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.22

Welcome to gatsby@4.22.0 release (August 2022 #3)

Key highlights of this release:

• Open RFCs

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

v4.21

Welcome to gatsby@4.21.0 release (August 2022 #2)

Key highlights of this release:

• gatsby-plugin-mdx v4
• Open RFCs

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

... (truncated)

Commits

• 5e5d565 chore(release): Publish
• be43418 fix(gatsby): Also clear cache on gatsby version change (#36913) (#36925)
• 012761e chore(release): Publish
• c9d97f9 fix(gatsby): track multiple root nodes and not just one (#36867) (#36879)
• 36211d1 adjust v4 release branch tests (#36881)
• c7f4cd7 chore: adjust base branch in assert changed files script
• 445800f chore(release): Publish
• d211a97 fix(gatsby-plugin-gatsby-cloud): Re-add constant LINK_REGEX (#36839) (#36847)
• 78bc932 chore(release): Publish
• 29fef67 fix(gatsby-page-utils): path creation on windows filesystem (#36766) (#36783)
• 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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/livecoders/website/network/alerts).