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 gatsby-plugin-offline from 2.0.21 to 3.10.2 #127

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

Conversation

dependabot-preview[bot]
Copy link

Bumps gatsby-plugin-offline from 2.0.21 to 3.10.2.

Release notes

Sourced from gatsby-plugin-offline's releases.

Release v2.32 (February 2021 #1)

Welcome to [email protected] release (February 2021. 1)

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

v2.31 (January 2021 #2)

Welcome to [email protected] release (January 2021 #2)

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

v2.30 (January 2021 #1)

Welcome to [email protected] release (January 2021 #‎1)

See full release notes

Key highlights of this release:

... (truncated)

Changelog

Sourced from gatsby-plugin-offline's changelog.

3.10.2 (2021-02-24)

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

3.10.1 (2021-02-18)

Bug Fixes

3.10.0 (2021-02-02)

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

3.10.0-next.0 (2021-01-18)

Bug Fixes

  • security: update vulnerable packages, include React 17 in peerDeps (#28545) (18b5f30)

3.9.0-next.1 (2021-01-12)

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

3.9.0-next.0 (2020-12-29)

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

3.8.0-next.2 (2020-12-29)

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

3.8.0-next.1 (2020-12-17)

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

3.8.0-next.0 (2020-12-10)

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

3.7.0-next.0 (2020-11-26)

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

3.6.0-next.0 (2020-11-18)

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

3.4.0-next.1 (2020-11-10)

... (truncated)

Commits
  • 6fa14e4 chore(release): Publish
  • 2035475 chore(release): Publish
  • 72c4a5a fix(gatsby-plugin-offline): Cache avif images (#29394) (#29429)
  • 7797522 chore(release): Publish
  • d4a8ad2 chore(release): Publish next pre-minor
  • 18b5f30 fix(security): update vulnerable packages, include React 17 in peerDeps (#28545)
  • 5e5c112 chore(release): Publish next
  • 2059ead chore(release): Publish next pre-minor
  • 968914f chore(release): Publish next
  • 762a524 chore(release): Publish next
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by ascorbic, a new releaser for gatsby-plugin-offline since your current version.


Dependabot compatibility score

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.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Feb 25, 2021
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