Repositories.md

Homebridge Repositories

Repository	Lead Collaborator	Publish Instructions
HAP-NodeJS	Supereg	New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
homebridge	Supereg	New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
homebridge-config-ui-x	oznu, bwp91	New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version

Supporting Packages

Repository	Lead Collaborator	Publish Instructions
bonjour	Supereg	New Latest Release If Pull Request is need to update Repo: 1. Merge pull request to latest 2. Wait for builds/tests to complete 3. A draft release, starting with a v, will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft Release with the Changelog info for of the new release 4. Click Publish Release to convert theDraft to Released 5. This will trigger what is needed to release new version of bonjour-hap If you are not working with a Pull Request: 1. Use the GitHub Action Release Drafter, to create a Draft Release. 2. Edit the Release Draft, and publish it. This will trigger the actions to build and publish a new version of bonjour-hap
fast-srp
ffmpeg-for-homebridge
dns-packet
ciao	Supereg	New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
camera-utils		New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
plugin-ui-utils		New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
hap-client		New Latest Release 1 - Merge pull request to latest 2 - Wait for builds/tests to complete 3 - A draft release will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft release with the Changelog info for the new release 4 - Click Publish Release to convert the Draft to Released 5 - This will trigger what is needed to release new version New Beta/Alpha Release 1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
wifi-connect
dbus-native
long.js
node_mdns
put
node-pty-prebuilt-multiarch		Build Instructions
nssm
ws-connect		New Beta Release 1 - Push to beta-*.*.* branch will generate new npm version New Latest Release For a production release, manually run the github action Build, Publish and Release. A Guthub and NPM release will be created.

Examples and Templates

Repository	Lead Collaborator	Publish Instructions
HAP-NodeJS-examples
homebridge-examples
homebridge-plugin-template
homebridge-plugin-camera-template

Documentation and WebSites

Repository	Lead Collaborator	Publish Instructions
homebridge.io
homebridge.github.io
branding
documentation
Analytics	NorthernMan54	The website automatically updates overnight on a daily basis via the github action Update Homebridge Analytics or via a manual workflow event

Other

Repository	Lead Collaborator	Publish Instructions
verified
plugin-repo
mdns-diagnostics
unmaintained-plugins
.github

Images and Containers

Repository	Lead Collaborator	Publish Instructions	Unique Dependencies*
homebridge-apt-pkg	NorthernMan54	High Level Workflow to Trigger a Release 1. Approve and merge Dependabot Pull Request ( triggers Stage 1 then 2 ) 2. Wait about an hour for builds and validation to occur. 3. Change Prerelease to Release and set status as Latest ( triggers Stage 3 then 4 ) The package.json and package-lock.json dependencies are used to manage the versions used within the release package. And Dependabot watches the versions, and creates a pull request if a version needs updating. Nothing else in package.json is used. If you manually update the dependencies, package-lock.json also needs updating. Then once a change is made to package.json/package-lock.json in the latest branch, originated by Depandabot, the stage 1 workflow will kick off. Detailed Build Instructions
homebridge-raspbian-image	NorthernMan54	New Latest Release If Pull Request is need to update Repo: 1. Merge pull request to latest 2. Wait for builds/tests to complete 3. A draft release, starting with a v, will be generated once the pull request is merged into the latest branch. If needed, update the tag and the description of the draft Release with the Changelog info for of the new release 4. Click Publish Release to convert theDraft to Released 5. This will trigger what is needed to release new version If you are not working with a Pull Request: 1. Create a release starting with a v ie v1.2.0 2. This will trigger what is needed to release new version Note: Both options will trigger the update of the Homebridge.io repo to the new rpi-image-repo.json	* homebridge-apt-pkg * wifi-connect
docker-homebridge	NorthernMan54	If you are not working with a Pull Request: 1. Use the GitHub Action Release Drafter, to create a Draft Release. 2. Edit the Release Draft, and publish it. This will trigger the actions to build and publish a new docker-homebridge package. New Latest Release 1. Merge pull request to latest 2. If Applicable, Wait for builds/tests to complete 3. A draft release will be generated from the pull request that was merged into the latest branch. If needed, update the tag and the description of the draft Release with the Changlog info for of the new release Note: Tag will be date pull request was merged 4. Click Publish Release to convert theDraft to Released 5. This will trigger the github action Build and Push Docker Images,. The TAG format for docker-homebridge is current date ie 2023-12-30.	* homebridge-apt-pkg * ffmpeg-for-homebridge
homebridge-syno-spk	NorthernMan54	Github Action - Build and Publish Manually start the workflow and enter a new release tag ie 1.0.46 Note: Version number must not contain a v, ie 1.1.0 and not v1.1.0 To rollback/unpublish a release, use the GitHub action Rollback / Replace Release file and enter the tag of a previous release.
homebridge-macos-pkg		Outdated
homebridge-vm-image		Outdated

• Please note, all images and containers are dependent on HAP-NodeJS / Homebridge and config-ui-x