testing-library / testing-library/dom-testing-library
Failing CI build
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 474
- PR merge metrics
- No merged PRs in 30d
Description
For a while now our CI build is red; I think this started somewhere at the end of 2024.
This is preventing builds (and releases) from going through, as well as people trying to run the project on their machines (#1353).
That's why I want to look into it, but I'm not sure of the best direction to take.
As far as I see it, we have two options:
- Update dependencies and create a new major release. I'm not a big fan of this as we don't have any vulnerabilities’ AFAIK.
- Pin the
@babel/helper-compilation-targetsversion, as I think this is the main culprit. This would look like #1341 - Something else ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by reproducing the red CI build and reviewing the dependency or CI configuration involved in @babel/helper-compilation-targets, then compare the proposed approach with #1341. Done means the CI build is green and builds and releases can proceed without breaking local project use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100