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

fix: allow nullable gatsbyImageData #217

Merged
merged 1 commit into from
Jan 4, 2022
Merged

Conversation

notrab
Copy link
Contributor

@notrab notrab commented Jan 4, 2022

No description provided.

@notrab notrab merged commit fb0867d into next Jan 4, 2022
@notrab notrab deleted the fix/nullable-gatsbyimagedata branch January 4, 2022 15:00
@github-actions
Copy link

github-actions bot commented Jan 4, 2022

🎉 This PR is included in version 2.7.0-next.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

notrab added a commit that referenced this pull request Jan 11, 2022
* feat: add support for Gatsby v4 (#206)

* ci: change node version to 14

* fix: remove return null (#215)

* fix: revert remove return null 215

This reverts commit 4939c84.

* fix: allow nullable gatsbyImageData (#217)

* chore: add additional fragments

* fix: use newer dependencies

* chore: use github actions v2

* fix: temp explicit rich text typenames

* docs: update readme

* fix: detect RichText automatically to create types

* docs(README): add note on Bad Request

* chore: cleanup demo Product fragment

* docs: add note about gatsby v4 (#207)

* feat: add support for Gatsby v4 (#206)

* docs(README): update install instructions

* fix: merge conflict

* docs(README): contributing note

* chore: fix contributors rc

Co-authored-by: João Pedro Schmitz <oi@joaopedro.cc>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant