gabrielsmborges / personal-playground

My React Portfolio Website
0 stars 0 forks source link

Bump http-cache-semantics, gatsby and gatsby-plugin-sharp in /packages/portfolio #23

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps http-cache-semantics to 4.1.1 and updates ancestor dependencies http-cache-semantics, gatsby and gatsby-plugin-sharp. These dependencies need to be updated together.

Updates http-cache-semantics from 4.1.0 to 4.1.1

Commits


Updates gatsby from 3.6.1 to 3.15.0

Release notes

Sourced from gatsby's releases.

v3.14 (September 2021 #1)

Welcome to gatsby@3.14.0 release (September 2021 #1)

This is the final minor release for gatsby v3. Gatsby v4 beta is already published behind the next npm tag and the next stable release will be gatsby@4.0.0. See what's inside!

We will keep publishing patches for 3.14.x with hotfixes until 4.0.0 stable is published and at least several weeks after.

Key highlights of this release:

Also, check out notable bugfixes.

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

v3.13 (August 2021 #3)

Welcome to gatsby@3.13.0 release (August 2021 #3)

Key highlights of this release:

Also check out notable bugfixes.

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

v3.12 (August 2021 #2)

Welcome to gatsby@3.12.0 release (August 2021 #2)

Key highlights of this release:

... (truncated)

Commits
  • c1e67a2 chore(release): Publish
  • 0c45654 chore: remove tracedSVG (#37093) (#37137)
  • d7edf95 chore(release): Publish
  • 2d00ea0 fix(gatsby-plugin-mdx): Do not leak frontmatter into page (#35859) (#35913)
  • 4997d63 chore(release): Publish
  • ff94ed5 fix(gatsby-plugin-mdx): don't allow JS frontmatter by default (#35830) (#35834)
  • 36f21b0 chore: Removate validate-renovate from v3-latest branch (#34460)
  • 1acb1bc chore(release): Publish
  • 1589bd8 fix(gatsby): ensure that writing node manifests to disk does not break on Win...
  • 9694010 fix(gatsby-source-drupal): Ensure all new nodes are created before creating r...
  • Additional commits viewable in compare view


Updates gatsby-plugin-sharp from 3.6.0 to 3.15.0

Release notes

Sourced from gatsby-plugin-sharp's releases.

v3.14 (September 2021 #1)

Welcome to gatsby@3.14.0 release (September 2021 #1)

This is the final minor release for gatsby v3. Gatsby v4 beta is already published behind the next npm tag and the next stable release will be gatsby@4.0.0. See what's inside!

We will keep publishing patches for 3.14.x with hotfixes until 4.0.0 stable is published and at least several weeks after.

Key highlights of this release:

Also, check out notable bugfixes.

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

v3.13 (August 2021 #3)

Welcome to gatsby@3.13.0 release (August 2021 #3)

Key highlights of this release:

Also check out notable bugfixes.

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

v3.12 (August 2021 #2)

Welcome to gatsby@3.12.0 release (August 2021 #2)

Key highlights of this release:

... (truncated)

Changelog

Sourced from gatsby-plugin-sharp's changelog.

Changelog: gatsby-plugin-sharp

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

5.5.0 (2023-01-24)

🧾 Release notes

Chores

5.4.0 (2023-01-10)

🧾 Release notes

Bug Fixes

Chores

5.3.2 (2022-12-14)

Note: Version bump only for package gatsby-plugin-sharp

5.3.1 (2022-12-14)

Note: Version bump only for package gatsby-plugin-sharp

5.3.0 (2022-12-13)

🧾 Release notes

Bug Fixes

Chores

5.2.0 (2022-11-25)

🧾 Release notes

... (truncated)

Commits


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/gabrielsmborges/personal-playground/network/alerts).