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

chore: bump dev dependencies #483

Merged
merged 3 commits into from
Jul 24, 2024
Merged

Conversation

scagood
Copy link
Contributor

@scagood scagood commented Jul 16, 2024

  1. Bumped all packages (except eslint) to the latest version.
  2. Replaced eslint-plugin-node with eslint-plugin-n

(#471)

@scagood

This comment was marked as resolved.

@scagood
Copy link
Contributor Author

scagood commented Jul 17, 2024

🤔 So now comes the time I need to know if we:

  • Keep supporting node versions for eslint v8 (Roll all versions back to points where 12.22)
  • Drop supporting node versions for eslint v8 (Bump package engines to match eslint v9 ^18.18.0 || ^20.9.0 || >=21.1.0) (eg in fc861bf)

@brettz9
Copy link
Member

brettz9 commented Jul 17, 2024

Can't we keep supporting ESLint v8 while bumping the Node requirements? We don't have to support every possible install which can handle ESLint 8.

@scagood
Copy link
Contributor Author

scagood commented Jul 17, 2024

Can't we keep supporting ESLint v8 while bumping the Node requirements? We don't have to support every possible install which can handle ESLint 8.

Ah, yes, sorry I miss wrote, you're 100% right, it'd be just dropping node versions for the eslint version! 😅

You can see that I left eslint v8 support in the mentioned commit 😶‍🌫️ fc861bf


edited original comment to cleanup the misunderstanding

@brettz9
Copy link
Member

brettz9 commented Jul 17, 2024

I think the bumped Node may also address your CI issues.

@scagood
Copy link
Contributor Author

scagood commented Jul 17, 2024

I think the bumped Node may also address your CI issues.

You'd be correct there :)


Will rebase if #484 is accepted

@brettz9 brettz9 added the chore label Jul 19, 2024
package.json Outdated Show resolved Hide resolved
Copy link

codecov bot commented Jul 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (bbcfcbf) to head (5cc5a43).
Report is 28 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #483   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        24    -1     
  Lines          649       661   +12     
  Branches       250       247    -3     
=========================================
+ Hits           649       661   +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@scagood scagood force-pushed the packages branch 3 times, most recently from d108a58 to a5dfa2b Compare July 24, 2024 08:38
@scagood scagood marked this pull request as ready for review July 24, 2024 09:11
@voxpelli voxpelli changed the title feat: Bump all packages to latest versions chore: bump dev dependencies Jul 24, 2024
@voxpelli voxpelli merged commit 197ae4e into eslint-community:main Jul 24, 2024
12 checks passed
@scagood scagood deleted the packages branch July 24, 2024 10:08
Copy link
Contributor Author

@scagood scagood left a comment

Choose a reason for hiding this comment

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

Its about now, I realised I missed actually posting these comments 👀

Comment on lines +99 to +100
🔧 Automatically fixable by the
[`--fix` CLI option](https://eslint.org/docs/user-guide/command-line-interface#--fix).
Copy link
Contributor Author

@scagood scagood Jul 24, 2024

Choose a reason for hiding this comment

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

There was a little fight between eslint-doc-generator and prettier here 🤔
Prettier seems to win...

Copy link
Member

Choose a reason for hiding this comment

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

Ugh, I would like to remove prettier :/

@@ -26,7 +26,7 @@
"lint": "npm-run-all \"lint:*\"",
"lint:eslint-docs": "npm run update:eslint-docs && git diff --exit-code",
"lint:js": "eslint --report-unused-disable-directives .",
"prepare": "husky install",
"prepare": "husky",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Im not sure what husky really brings to the table.

The entire husky package looks to be replaceable with one command:

git config core.hooksPath .husky

Copy link
Member

Choose a reason for hiding this comment

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

It at least brings convention, I like it sometimes

voxpelli pushed a commit that referenced this pull request Aug 6, 2024
🤖 I have created a release *beep* *boop*
---


##
[7.1.0](v7.0.0...v7.1.0)
(2024-08-06)


### 🌟 Features

* **`catch-or-return`, `prefer-await-to-then`:** do not report Cypress
commands
([#495](#495))
([943f162](943f162))
* **`prefer-await-to-then`:** ignore constructor scope unless with
`strict` option
([#496](#496))
([7bffb7a](7bffb7a))
* new rule `spec-only` to check for non-spec Promise methods
([#502](#502))
([d6e9de1](d6e9de1))


### 📚 Documentation

* fixes the CI readme badge
([#511](#511))
([030a3be](030a3be))
* supply missing docs
([#503](#503))
([602d825](602d825))


### 🧹 Chores

* bump dev dependencies
([#483](#483))
([197ae4e](197ae4e))
* **deps-dev:** bump husky from 9.1.1 to 9.1.2
([#516](#516))
([ab8e7a0](ab8e7a0))
* file extension missing
([#519](#519))
([94c9834](94c9834))
* fix format.yml
([#507](#507))
([948c097](948c097))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+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
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants