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

Cleanup repo #459

Merged
merged 1 commit into from Mar 4, 2020
Merged

Conversation

MichaelDeBoey
Copy link
Member

No description provided.

@codesandbox-ci
Copy link

codesandbox-ci bot commented Mar 4, 2020

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 21adad1:

Sandbox Source
determined-sound-wu05q Configuration

@codecov
Copy link

codecov bot commented Mar 4, 2020

Codecov Report

Merging #459 into beta will not change coverage by %.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              beta      #459   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          412       412           
  Branches        98        98           
=========================================
  Hits           412       412           

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 5fae126...21adad1. Read the comment docs.

Copy link
Member

@kentcdodds kentcdodds left a comment

Choose a reason for hiding this comment

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

Cool, thank you!

@kentcdodds kentcdodds merged commit a3c15bf into testing-library:beta Mar 4, 2020
@MichaelDeBoey MichaelDeBoey deleted the cleanup-repo branch March 4, 2020 20:21
@kentcdodds
Copy link
Member

@all-contributors please add @MichaelDeBoey for code

@allcontributors
Copy link
Contributor

@kentcdodds

I've put up a pull request to add @MichaelDeBoey! 🎉

@kentcdodds
Copy link
Member

🎉 This PR is included in version 7.0.0-beta.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

kentcdodds added a commit that referenced this pull request Mar 4, 2020
Closes #430

BREAKING CHANGE: This drops support for Node 8. Node 10 or greater is now required.
kentcdodds added a commit that referenced this pull request Mar 4, 2020
Closes #430

BREAKING CHANGE: This drops support for Node 8. Node 10 or greater is now required.
@NMinhNguyen
Copy link
Contributor

Sorry to be commenting on a merged PR, but any chance the Node v10 requirement could be made a tiny bit lower, e.g. 10.12 (ESLint) or 10.13 (Jest)? Reason being I work in a big corporate where updating to the latest Node version isn't as easy as I would like it to be 😔 I understand that this is not directly this package's problem, but would like to understand why 10.18 specifically and not a bit lower?

@kentcdodds
Copy link
Member

Pretty sure we could manage regular node 10 actually

NMinhNguyen added a commit to NMinhNguyen/dom-testing-library that referenced this pull request Mar 6, 2020
@NMinhNguyen NMinhNguyen mentioned this pull request Mar 6, 2020
4 tasks
NMinhNguyen added a commit to NMinhNguyen/dom-testing-library that referenced this pull request Mar 6, 2020
kentcdodds pushed a commit that referenced this pull request Mar 6, 2020
This is a follow-up to #459.
@MichaelDeBoey
Copy link
Member Author

@NMiinhNguyen I've set the minimum requirement to v10.18, because semantic-release@17, requires it
https://github.com/semantic-release/semantic-release/releases/tag/v17.0.0

@kentcdodds
Copy link
Member

But we only use semantic release when we're releasing the package and we only do today with node 12

@MichaelDeBoey
Copy link
Member Author

MichaelDeBoey commented Mar 6, 2020

Edit: Whoops wrong library 😅 We're indeed only using it with Node 12, so we should look at all the other dependencies to see which would be the minimum Node version

We do, but users of the travis-release script can make another choice if they want:

// example of a possible .travis.yml

jobs:
  include:
    - stage: release
      node_js: 10.13
      script: kcd-scripts travis-release

@NMinhNguyen
Copy link
Contributor

@MichaelDeBoey as far as the consumption of this library is concerned, semantic-release is not relevant because it's not a direct dependency of this package and is used when releasing only.

@kentcdodds
Copy link
Member

In any case, I think Node 10 is the version I want my packages supporting and if we have a dep that prevents that then we should change the dep or did the dep.

kentcdodds added a commit that referenced this pull request Mar 12, 2020
Closes #430

BREAKING CHANGE: This drops support for Node 8. Node 10 or greater is now required.
kentcdodds added a commit that referenced this pull request Mar 12, 2020
Closes #430

BREAKING CHANGE: This drops support for Node 8. Node 10 or greater is now required.
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

3 participants