Skip to content

Latest commit

 

History

History
68 lines (56 loc) · 10.3 KB

Repositories.md

File metadata and controls

68 lines (56 loc) · 10.3 KB
Raw

Homebridge Repositories

Repository Lead Collaborator Publish Instructions
HAP-NodeJS Supereg
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 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
Note: Release will not start with a v
5 - This will trigger what is need to release new version

New Beta/Alpha Release
1 - Push to beta-*.*.*/alpha-*.*.* branch will generate new npm version
2 - If you would like to Attach Artifacts (tar.gz) for the beta/alpha release, create a pre-release with a tag like 4.52.0-beta.49
Note: needs to match the beta NPM version
3 - This will trigger what is needed to generate the Artifacts for that beta version

Supporting Packages

Repository Lead Collaborator Publish Instructions
bonjour Supereg Release Workflow ( Beta --> Production )

1 - Determine what the target version will be for the final release and update the package.json version number ( ie 0.5.6)
2 - Create a new branch including the target release version ie beta-0.5.6
3 - Commit the updated package.json to the new beta branch. This will trigger a npm release with the beta tag, and the npm version set to 0.5.6-beta.0.
4 - As updates are made to the beta branch, npm beta releases will be created.
5 - Once the release is complete, and ready for latest/production release, create a pull request to merge the changes into the latest branch.
6 - After reviews are complete, merge the pull request
7 - For the latest/production release, the workflow must be manually kicked off / started from Actions --> Build and Publish
8 - Delete beta branch
fast-srp
ffmpeg-for-homebridge
dns-packet
ciao Supereg
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

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

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 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 and publish to DEB Repo

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 and publish to DEB Repo
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 Before publishing, the HOMEBRIDGE_PKG_VERSION & FFMPEG_VERSION in the Dockerfile need to be updated with the latest, current versions.

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 Work in progress
homebridge-vm-image Outdated
  • Please note, all images and containers are dependent on HAP-NodeJS / Homebridge and config-ui-x