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: don't consider concurrent.skip and concurrent.only valid test functions #1124

Merged
merged 1 commit into from May 28, 2022

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented May 28, 2022

To be merged after #1122 is landed

@G-Rath G-Rath added the bug label May 28, 2022
@G-Rath G-Rath force-pushed the remove-invalid-fn-chains branch 2 times, most recently from 1d29acb to a9f5b28 Compare May 28, 2022 18:40
@G-Rath G-Rath marked this pull request as ready for review May 28, 2022 18:41
@G-Rath G-Rath merged commit 0aa5eb6 into main May 28, 2022
@G-Rath G-Rath deleted the remove-invalid-fn-chains branch May 28, 2022 19:19
github-actions bot pushed a commit that referenced this pull request May 28, 2022
## [26.4.2](v26.4.1...v26.4.2) (2022-05-28)

### Bug Fixes

* don't consider `concurrent.skip` and `concurrent.only` valid test functions ([#1124](#1124)) ([0aa5eb6](0aa5eb6))
* **no-disabled-tests:** use jest function call parser for checking number of args ([#1126](#1126)) ([b67e389](b67e389))
@github-actions
Copy link

🎉 This PR is included in version 26.4.2 🎉

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant