-
-
Notifications
You must be signed in to change notification settings - Fork 630
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
latest <- beta #1027
latest <- beta #1027
Conversation
@Supereg would you be happy with a 0.12.0 release of hap-nodejs soon? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates and regeneration of the docs 👍
* - `info.username` - formatted as a MAC address, like `CC:22:3D:E3:CE:F6`, of this accessory. | ||
* Must be globally unique from all Accessories on your local network. | ||
* - `info.pincode` - the 8-digit pin code for clients to use when pairing this Accessory. | ||
* Must be formatted as a string like `031-45-154`. | ||
* - `info.category` - one of the values of the `Accessory.Category` enum, like `Accessory.Category.SWITCH`. | ||
* This is a hint to iOS clients about what "type" of Accessory this represents, so | ||
* that for instance an appropriate icon can be drawn for the user while adding a | ||
* new Accessory. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for improve documentation here 🚀
@bwp91 how about we finally tag a |
I'm happy to along with any versioning that you suggest. Agreed that with a 1.0.0 we can take the opportunity to really specify that the officially supported node versions are 18 and 20. I'm not actually sure whether it would still run on e.g. node 16. |
Nothing from me. My main focus here is to get a version of hap-nodejs published with updated dependencies, then work my way through homebridge itself and the UI with updated hap-nodejs |
i merged into latest branch, maybe i will await further instruction on release version! |
Tagging a 1.0 sounds good to me 👍
Thanks for the hard work there 🚀 |
Not with a memory leak still hanging out there…@Supereg, I’d suggest holding off for a bit there. |
@hjdhjd happy with a 0.12.0 release until memory leak is fixed and then bumping to 1.0.0? |
feel free to not review the
/docs
folder 😆Changed
CHANGELOG.md
fileREADME.md
package-lock.json
(no major changes to dep versions)