chore(deps-dev): bump gatsby from 4.6.2 to 4.7.1 #7591
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/gatsby-4.7.1
branch
from
2d9bea5
to
6785837
Compare
|
Failures appear legitimate, ostensibly more typedef drift npm run check-types:frontend
> shields.io@0.0.0 check-types:frontend
> tsc --noEmit --project .
node_modules/graphql-compose/lib/type/buffer.d.ts:3:25 - error TS2315: Type 'GraphQLScalarType' is not generic.
3 declare const _default: GraphQLScalarType<Buffer, string>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
node_modules/graphql-compose/lib/type/date.d.ts:2:25 - error TS2315: Type 'GraphQLScalarType' is not generic.
2 declare const _default: GraphQLScalarType<Date, string>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 2 errors.
Exited with code exit status 2
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/gatsby-4.7.1
branch
from
6785837
to
4d1a3fe
Compare
|
In general I'm a little curious why we see these types of issues at the frequency we've been seeing them (not every day of course but frequently enough to stick in the brain). I've seen and can understand cases where the typedefs are maintained by a separate individual/team and distributed via DefinitelyTyped vs. being bundled in with the main/source js pacakge. Gatsby's in the latter camp, so haven't ever really wrapped my head around what would could be the root cause (admittedly i may be conflating similar issues from the various gatsby plugins/components) |
Bumps [gatsby](https://github.com/gatsbyjs/gatsby) from 4.6.2 to 4.7.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/gatsby@4.6.2...gatsby@4.7.1) --- updated-dependencies: - dependency-name: gatsby dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/gatsby-4.7.1
branch
from
4d1a3fe
to
3dd8e72
Compare
|
Superseded by #7624. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps gatsby from 4.6.2 to 4.7.1.
Release notes
Sourced from gatsby's releases.
Commits
f672a67chore(release): Publish07dccadfix(gatsby-link): trailing slash undefined check for prod env (#34765) (#34766)1f30882chore(release): Publish9e8dd90chore(docs): UpdatetransformOptionsdefaults (#34713)72b3586chore(starter): Add minimal Typescript starter (#34688)62b07a0chore(docs): Added requiredtypeattribute to resolver (#34716)0c04ce0chore(docs): Update "Debugging HTML builds" to includegetServerData(#34631)4ce7693chore(changelogs): update changelogs (#34739)e8d99ddchore(docs): update PurgeCSS instructions for Tailwind 3 (#34726)4b802adFix polling logic for non eager redirected urls. (#34712)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)