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

Test for composite: true errors in CI, ensuring we can't ship those issues #501

Merged
merged 10 commits into from
Feb 26, 2024

Conversation

jpwilliams
Copy link
Member

@jpwilliams jpwilliams commented Feb 23, 2024

Summary

We've seen some issues crop up when composite: true is present in tsconfig.json files. This PR adds a composite: 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 PR N/A Bug fix and testing
  • Added unit/integration tests
  • Added changesets if applicable

Related

@jpwilliams jpwilliams added Bug Something isn't working prerelease/inngest Create snapshot releases for a PR for the "inngest" package. labels Feb 23, 2024
@jpwilliams jpwilliams self-assigned this Feb 23, 2024
Copy link

changeset-bot bot commented Feb 23, 2024

🦋 Changeset detected

Latest commit: 7ed04c1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
inngest Patch

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

@inngest-release-bot inngest-release-bot added the 📦 inngest Affects the `inngest` package label Feb 23, 2024
@inngest-release-bot
Copy link
Collaborator

inngest-release-bot commented Feb 23, 2024

A user has added the prerelease/inngest label, so this PR will be published to npm with the tag pr-501. It will be updated with the latest changes as you push commits to this PR.

You can install this prerelease version with:

npm install inngest@pr-501

The last release was built and published from 7ed04c1.

@jpwilliams jpwilliams marked this pull request as ready for review February 23, 2024 20:31
Copy link
Member

@djfarrelly djfarrelly left a 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 👏

Comment on lines +34 to +35
This code is only built and is never run, so don't worry about it actually
working.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😆

@jpwilliams jpwilliams merged commit 0048c94 into main Feb 26, 2024
35 checks passed
@jpwilliams jpwilliams deleted the fix/composite-regression-tests branch February 26, 2024 11:49
jpwilliams pushed a commit that referenced this pull request Feb 26, 2024
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working 📦 inngest Affects the `inngest` package prerelease/inngest Create snapshot releases for a PR for the "inngest" package.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants