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

Release @latest #420

Merged
merged 1 commit into from
Dec 12, 2023
Merged

Release @latest #420

merged 1 commit into from
Dec 12, 2023

Conversation

inngest-release-bot
Copy link
Collaborator

@inngest-release-bot inngest-release-bot commented Dec 11, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

  • #421 471d11f Thanks @jpwilliams! - Fix serverless use of inngest/next with next@>=13.0.0 <13.5.0 failing to return a response, as well as next@>=13.5.0 logging the same error

@inngest/[email protected]

Patch Changes

@inngest-release-bot inngest-release-bot added the 📦 inngest Affects the `inngest` package label Dec 12, 2023
@jpwilliams jpwilliams self-assigned this Dec 12, 2023
@jpwilliams jpwilliams merged commit 0242656 into main Dec 12, 2023
35 checks passed
@jpwilliams jpwilliams deleted the changeset-release/main branch December 12, 2023 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants