Skip to content

test: Ensure broken node 16.9.0 isn't used #1028

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

Merged
merged 3 commits into from
Sep 11, 2021

Conversation

eps1lon
Copy link
Member

@eps1lon eps1lon commented Sep 11, 2021

What:

Fix GitHub jobs using node 16

Why:

They're currently broken due to using the cached and broken node version 16.9.0 which causes jest to fail due to

How:

Cherry-pick using a working version which works in a previously failing job: https://github.com/testing-library/dom-testing-library/runs/3574134403

Checklist:

  • [ ] Documentation added to the
    docs site
  • Tests
  • [ ] TypeScript definitions updated
  • Ready to be merged

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 135f09d:

Sandbox Source
react-testing-library-examples Configuration

@codecov
Copy link

codecov bot commented Sep 11, 2021

Codecov Report

Merging #1028 (135f09d) into main (7b125de) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main     #1028   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        25           
  Lines          916       916           
  Branches       286       286           
=========================================
  Hits           916       916           
Flag Coverage Δ
node-12 100.00% <ø> (ø)
node-14 100.00% <ø> (ø)
node-16.9.1 100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b125de...135f09d. Read the comment docs.

@@ -18,7 +18,8 @@ jobs:
# Otherwise we would not know if the problem is tied to the Node.js version
fail-fast: false
matrix:
node: [12, 14, 16]
# TODO: relax `'16.9.1'` to `16` once GitHub has 16.9.1 cached. 16.9.0 is broken due to https://github.com/nodejs/node/issues/40030
node: [12, 14, '16.9.1']
Copy link
Member Author

@eps1lon eps1lon Sep 11, 2021

Choose a reason for hiding this comment

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

Can't use '^16.9.1' because codecov flags do not support carets:

Flags Must consist only of alphanumeric characters, '_', '-', or '.' and not exceed 45 characters

-- https://docs.codecov.com/docs/flags

@eps1lon eps1lon changed the title ensure we install past ^16.9.1? test: Ensure broken node 16.9.0 isn't used Sep 11, 2021
@eps1lon eps1lon merged commit 74c63b7 into testing-library:main Sep 11, 2021
@eps1lon eps1lon deleted the test/working-node16 branch September 11, 2021 08:45
@github-actions
Copy link

🎉 This PR is included in version 8.4.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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant