-
Notifications
You must be signed in to change notification settings - Fork 41
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
Test for composite: true
errors in CI, ensuring we can't ship those issues
#501
Conversation
🦋 Changeset detectedLatest commit: 7ed04c1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
A user has added the prerelease/inngest label, so this PR will be published to npm with the tag You can install this prerelease version with: npm install inngest@pr-501 The last release was built and published from 7ed04c1. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Tested on my own project as well - works great! Thank you Jack 👏
This code is only built and is never run, so don't worry about it actually | ||
working. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😆
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## inngest@3.15.1 ### Patch Changes - [#501](#501) [`0048c94`](0048c94) Thanks [@jpwilliams](https://github.com/jpwilliams)! - Fix failures for `composite: true` errors Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Summary
We've seen some issues crop up when
composite: true
is present intsconfig.json
files. This PR adds acomposite: true
project where we test the Inngest package for compliance for the types that it exports.We purposefully want to limit the number of types exported from the main
"inngest"
entrypoint, as each type exported here becomes part of the public API, where changing those types is a breaking change. Therefore, the composite check gives us a (albeit inaccurate) test that can stop us shipping these dangerous changes.Checklist
Added a docs PR that references this PRN/A Bug fix and testingRelated
composite
#384composite
setting #385composite
setting #460