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.

Sign up for GitHub

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

Jump to bottom

fix: explicit support for node 18 #386

Merged
merged 1 commit into from
Oct 13, 2023
Merged

fix: explicit support for node 18 #386

merged 1 commit into from
Oct 13, 2023

Conversation

t-col
Copy link
Contributor

@t-col t-col commented Oct 13, 2023 •
edited
Loading

bumping the package version to release previous commits that fixed support for node 18:

@t-col t-col requested a review from a team as a code owner October 13, 2023 17:08
@t-col t-col enabled auto-merge (squash) October 13, 2023 17:09
@t-col t-col merged commit b861f8a into master Oct 13, 2023
2 checks passed
@t-col t-col deleted the fix/node-18-support branch October 13, 2023 17:12
contentful-automation bot added a commit that referenced this pull request Oct 26, 2023
@contentful-automation
chore(release): 2.8.0 [skip ci]
b7f6b0e 
# [2.8.0](v2.7.2...v2.8.0) (2023-10-26)

### Bug Fixes

* explicit support for node 18 ([#386](#386)) ([b861f8a](b861f8a))
* trigger new build ([951153d](951153d))

### Features

* make graphQLOutputType optional ([#402](#402)) ([b45ec75](b45ec75))
@contentful-automation
Copy link
Contributor

🎉 This PR is included in version 2.8.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jjolton-contentful jjolton-contentful jjolton-contentful approved these changes

Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@t-col @jjolton-contentful