Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump parse-path and gatsby #34

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 6, 2022

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

⭐ This is a major release of parse-path! ⭐

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! 😊

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

Updates gatsby from 2.25.3 to 5.2.0

Release notes

Sourced from gatsby's releases.

v5.2.0

Welcome to [email protected] release (November 2022 #3)

This is an out of band release due to the removal of the Potrace library in Gatsby. We'll continue with our biweekly schedule as normal.

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

v5.1.0

Welcome to [email protected] release (November 2022 #2)

This is the first minor release after the recent major release of Gatsby 5! We are focused on your feedback and implementing fixes as needed.

If you haven’t migrated yet, please refer to the migration guide. We’ve done our best to make the transition smooth!

Some brief notes about what Gatsby 5 brings to the table:

  • Slices API unlocks up to 90% reduction in build duration for content changes in highly shared components
  • Partial Hydration allows you to ship only the necessary JavaScript to the browser

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

v5.0.0

Welcome to [email protected] release (November 2022 #1)

Key highlights of this release:

Major dependency updates:

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

v4.24

Welcome to [email protected] release (September 2022 #2)

Key highlights of this release:

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

... (truncated)

Commits
  • cec2ab0 chore(release): Publish
  • 94c2d73 chore: remove tracedSVG (#37093)
  • 0889d31 fix(gatsby): Sanitize length on objects (#34253)
  • c935f05 chore(gatsby-plugin-image): Add peerDependenciesMeta (#35146)
  • 0b3c34c chore(docs): Update "Working with Images in Markdown" (#34621)
  • 21cbfb3 fix(gatsby): stale node manifests (#37091)
  • ce0d8b2 chore(docs): Clarify MDX sourcing instructions (#37088)
  • 53a68c6 chore(docs): Update building with components
  • a259ff8 docs: add onCreateNode params and example (#27503)
  • fb15745 fix(deps): update dependency contentful to ^9.1.34 for gatsby-source-contentf...
  • 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.

Bumps [parse-path](https://github.com/IonicaBizau/parse-path) to 7.0.0 and updates ancestor dependency [gatsby](https://github.com/gatsbyjs/gatsby). These dependencies need to be updated together.


Updates `parse-path` from 4.0.2 to 7.0.0
- [Release notes](https://github.com/IonicaBizau/parse-path/releases)
- [Commits](IonicaBizau/parse-path@4.0.2...7.0.0)

Updates `gatsby` from 2.25.3 to 5.2.0
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/compare/[email protected]@5.2.0)

---
updated-dependencies:
- dependency-name: parse-path
  dependency-type: indirect
- dependency-name: gatsby
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants