Skip to content
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.

chore(deps): bump http-cache-semantics, gatsby, gatsby-plugin-sharp and npm-check-updates #6

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

chore(deps): bump http-cache-semantics, gatsby, gatsby-plugin-sharp and npm-check-updates #6

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 11, 2023

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

Updates http-cache-semantics from 3.8.1 to 4.1.1

Commits

Updates gatsby from 2.17.7 to 5.8.1

Release notes

Sourced from gatsby's releases.

v5.7.0

Welcome to [email protected] release (February 2023 #2)

This release focused on bug fixes and perf improvements. Check out notable bugfixes and improvements.

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

v5.6.0

Welcome to [email protected] release (February 2023 #1)

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

Full changelog

v5.5.0

Welcome to [email protected] release (January 2023 #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

Full changelog

v5.4.0

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

The whole team took time off for a much deserved winter break and we hope you had relaxing holidays, too! Before the break we spent time doing maintenance work such as updating internal dependencies or fixing some smaller bugs here and there. In case you missed it, we shipped ES Modules (ESM) in Gatsby files in the last release.

So check out the notable bugfixes section to learn more.

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
  • 12c91db chore(release): Publish
  • 5f44208 fix(gatsby-plugin-sharp): don't serve static assets that are not result of cu...
  • facb07f fix(gatsby): don't block event loop during inference (#37780) (#37800)
  • 7d4125b chore(release): Publish
  • 944b074 fix(gatsby-source-shopify): Correct interface query (#37788) (#37791)
  • 370ba2a chore(release): Publish
  • 0f838b2 feat(gatsby-source-shopify): use gatsby node id to enable relationships (#377...
  • b1abb5b chore(release): Publish
  • 5e2c979 chore(deps): update starters and examples to ^18.15.3 (#37759)
  • 7bda38a feat:(gatsby-cli) - support REACT_PROFILE env var value to set profile cli ar...
  • Additional commits viewable in compare view

Updates gatsby-plugin-sharp from 2.2.36 to 2.14.4

Changelog

Sourced from gatsby-plugin-sharp's changelog.

2.14.4 (2021-05-04)

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

2.14.3 (2021-02-25)

Other Changes

2.14.2 (2021-02-24)

Bug Fixes

2.14.1 (2021-02-05)

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

2.14.0 (2021-02-02)

🧾 Release notes

Features

Bug Fixes

Chores

  • update minor and patch for gatsby-plugin-sharp #28968 (17bb011)

2.13.4 (2021-01-29)

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

2.13.3 (2021-01-28)

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

2.13.2 (2021-01-26)

... (truncated)

Commits

Updates npm-check-updates from 3.1.26 to 16.10.8

Release notes

Sourced from npm-check-updates's releases.

v16.10.0

Feature

  • Added filterResults option to filter out upgrades based on a user provided function.

filterResults runs after new versions are fetched, in contrast to filter and filterVersion, which run before. This allows you to filter out upgrades with filterResults based on how the version has changed (e.g. a major version change).

Only available in .ncurc.js or when importing npm-check-updates as a module.

/** Filter out non-major version updates.
  @param {string} packageName               The name of the dependency.
  @param {string} currentVersion            Current version declaration (may be range).
  @param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be range).
  @param {string} upgradedVersion           Upgraded version.
  @param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
  @returns {boolean}                        Return true if the upgrade should be kept, otherwise it will be ignored.
*/
filterResults: (packageName, {currentVersion, currentVersionSemver, upgradedVersion, upgradedVersionSemver}) => {
  const currentMajorVersion = currentVersionSemver?.[0]?.major
  const upgradedMajorVersion = upgradedVersionSemver?.major
  if (currentMajorVersion && upgradedMajorVersion) {
    return currentMajorVersion < upgradedMajorVersion
  }
  return true
}

For the SemVer type definition, see: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring

Thanks to mslowiak for this enhancement!

v16.8.0

Feature

  • Added --format lines
$ ncu --format lines
@ava/typescript@^4.0.0
ava@^5.2.0
eslint@^8.36.0
lerna@^6.5.1
typescript@^5.0.2

This is particularly useful for upgrading global modules:

npm install -g $(ncu -g --format lines)
</tr></table>

... (truncated)

Changelog

Sourced from npm-check-updates's changelog.

Changelog

This file documents all major version releases. For other releases, please read the commit history.

[16.0.0] - 2022-07-23

Breaking

  • Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior.
  • Wild card filters now apply to scoped packages. Previously, ncu -f '*vite*' would not include @vitejs/plugin-react. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.

raineorshine/npm-check-updates@v15.3.4...v16.0.0

[15.0.0] - 2022-06-30

Breaking

  • node >= 14.14 is now required (#1145)
    • Needed to upgrade update-notifier with has a moderate severity vulnerability
  • yarn autodetect has been improved (#1148)
    • This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
    • More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

raineorshine/npm-check-updates@v14.1.1...v15.0.0

[14.0.0] - 2022-06-16

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre 1 or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

  • You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

[13.0.0] - 2022-05-15

Breaking

  • node >= 14 is now required
  • Several options which have long been deprecated have been removed:
    • --greatest - Instead use --target greatest

... (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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
chore(deps): bump http-cache-semantics, gatsby, gatsby-plugin-sharp a…
f4e9586 
…nd npm-check-updates

Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) to 4.1.1 and updates ancestor dependencies [http-cache-semantics](https://github.com/kornelski/http-cache-semantics), [gatsby](https://github.com/gatsbyjs/gatsby), [gatsby-plugin-sharp](https://github.com/gatsbyjs/gatsby/tree/HEAD/packages/gatsby-plugin-sharp) and [npm-check-updates](https://github.com/raineorshine/npm-check-updates). These dependencies need to be updated together.


Updates `http-cache-semantics` from 3.8.1 to 4.1.1
- [Release notes](https://github.com/kornelski/http-cache-semantics/releases)
- [Commits](kornelski/http-cache-semantics@v3.8.1...v4.1.1)

Updates `gatsby` from 2.17.7 to 5.8.1
- [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.8.1)

Updates `gatsby-plugin-sharp` from 2.2.36 to 2.14.4
- [Release notes](https://github.com/gatsbyjs/gatsby/releases)
- [Changelog](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sharp/CHANGELOG.md)
- [Commits](https://github.com/gatsbyjs/gatsby/commits/[email protected]/packages/gatsby-plugin-sharp)

Updates `npm-check-updates` from 3.1.26 to 16.10.8
- [Release notes](https://github.com/raineorshine/npm-check-updates/releases)
- [Changelog](https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md)
- [Commits](raineorshine/npm-check-updates@v3.1.26...v16.10.8)

---
updated-dependencies:
- dependency-name: http-cache-semantics
  dependency-type: indirect
- dependency-name: gatsby
  dependency-type: direct:production
- dependency-name: gatsby-plugin-sharp
  dependency-type: direct:production
- dependency-name: npm-check-updates
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants