Skip to content

chore: update dependencies #3436

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

Closed
wants to merge 3 commits into from
Closed

chore: update dependencies #3436

wants to merge 3 commits into from

Conversation

bwp91
Copy link
Contributor

@bwp91 bwp91 commented Sep 18, 2023

♻️ Current situation

  • some dependencies are out of date
  • gitignore file does not include coverage directory
  • package.json engine node versions are at node v10 (we now only support 18, but have added 20 too)

I would like to start looking into updating some dependencies into their major new versions but wanted to get this done as the first stepping stone.

💡 Proposed solution

  • updates dependencies to latest minor/patch versions
  • updates devDependensies to some latest major/minor/patch versions
  • full refresh of package-lock.json
  • include coverage in gitignore file
  • update package.json file engines - node - to ^16.20.2 || ^18.17.1

⚙️ Release Notes

chore: update dependencies

Testing

no tests changes, but all are passing

Reviewer Nudging

🤷‍♂️

@coveralls
Copy link

coveralls commented Sep 18, 2023

Pull Request Test Coverage Report for Build 6228060496

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 26.032%

Totals Coverage Status
Change from base Build 5598271589: 0.0%
Covered Lines: 392
Relevant Lines: 1365

💛 - Coveralls

package.json Outdated
@@ -33,7 +33,7 @@
"homebridge": "bin/homebridge"
},
"engines": {
"node": ">=10.17.0"
"node": "^16.20.2 || ^18.17.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

The synology package is using a slightly older Node 18 package nodejs.org 18.15.0-1008

So minimum version needs to take this into account

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @NorthernMan54 I set minimum engine node version to 18.15.0.

I would preferably like to push this into a beta branch of homebridge rather than master, but not totally sure how it works on this repo

@bwp91
Copy link
Contributor Author

bwp91 commented Sep 18, 2023

Hi @NorthernMan54

The node engine part was an extra I did, not sure if was really necessary or not. Have updated the downgrade of 18.

But I also want to make it clear that these are the versions of node that homebridge supports, not necessarily the versions of node that homebridge will work with

donavanbecker
donavanbecker previously approved these changes Sep 18, 2023
Copy link
Contributor

@donavanbecker donavanbecker left a comment

Choose a reason for hiding this comment

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

Need this beta.

@bwp91
Copy link
Contributor Author

bwp91 commented Sep 21, 2023

@donavanbecker which is latest beta branch?

@donavanbecker
Copy link
Contributor

would think beta-1.6.1

@bauer-andreas bauer-andreas changed the base branch from master to beta-1.6.2 September 22, 2023 07:46
@bauer-andreas bauer-andreas dismissed donavanbecker’s stale review September 22, 2023 07:46

The base branch was changed.

@bauer-andreas bauer-andreas changed the base branch from beta-1.6.2 to 1.7.0 September 22, 2023 07:47
@bauer-andreas
Copy link
Member

@donavanbecker which is latest beta branch?

Assuming, we are fine with a minor bump, I just created a 1.7.0 beta right now.

@donavanbecker
Copy link
Contributor

Thanks @Supereg, @bwp91 looks like we can get rid of all of the other beta branches also

@donavanbecker donavanbecker self-requested a review October 28, 2023 06:54
@donavanbecker
Copy link
Contributor

@bwp91, I think we are good to go on this. Unless there is something else you want to add. new beta was published for this: v1.7.0-beta.0

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.

5 participants