ben
/
build-hass
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity
53 Commits 3 Branches 1 Tag 191 KiB
Dockerfile 52.1%
Shell 47.9%
Go to file
ben 63c24f5101
ben/build-hass/pipeline/head This commit looks good Details
uv 0.2.27 		2024-09-04 19:38:18 +02:00
.pipeline set HASS_VERSION with arg 2024-09-04 19:26:55 +02:00
docker/bin try uv 2024-03-29 00:30:52 +01:00
img absolute unit 2023-10-12 07:47:12 +02:00
upstream-container musl-dev and pybluez-dev apk packages for pybluez 2024-05-16 18:17:00 +02:00
.dockerignore dont always publish 2024-05-03 23:55:35 +02:00
.gitignore dont always publish 2024-05-03 23:55:35 +02:00
Dockerfile uv 0.2.27 2024-09-04 19:38:18 +02:00
Dockerfile.from-virtualenv slightly more "standard" 2023-12-30 02:22:18 +01:00
Jenkinsfile delete dir 2024-08-29 00:58:39 +02:00
LICENSE Initial commit 2023-09-28 15:37:11 +00:00
README.md github api to get latest release 2024-02-29 02:14:10 +01:00
apk_list.txt apk packages in upstream 2023-12-17 05:57:31 +01:00
hassfest-requirements.txt create requirements file needed to use hassfest 2024-03-30 19:07:47 +01:00

README.md

build-hass

Build Status version git github matrix

Home Assistant logo

Get latest release

Reading the git tags is a bit unreliable. Another way to do it would be to use the GitHub REST API to get the latest release.

$ curl -s https://api.github.com/repos/home-assistant/core/releases/latest | jq .name
"2024.2.5"

This is probably easier, and does not require auth (for public repos). The returned JSON contains a whole bunch of fields and info, this may not be the right one. Open the API URL in Firefox and take a look.