Add more data to the versioning file and convert it to json#103
Add more data to the versioning file and convert it to json#103crschardt merged 1 commit intoPhotonVision:mainfrom
Conversation
samfreund
force-pushed
the
versioning
branch
2 times, most recently
from
d077269 to
7b2016f
Compare
|
|
||
| # Add photon version file | ||
| mkdir -p /opt/photonvision/ | ||
| echo "${GITHUB_REF_NAME};${image_name}" > /opt/photonvision/image-version |
There was a problem hiding this comment.
should we leave this here for compatibility with older versions of PhotonVision? If someone installs 2025.3.1 on a newer image, it won't find the version information. Deprecate it and we'll remove it in a future version.
There was a problem hiding this comment.
done, I deprecated it for '27
There was a problem hiding this comment.
Installing 2025.3.1 on a newer image won't work for libcamera ABI compat, and I don't think we should be really supporting inter year flashing anyways?
There was a problem hiding this comment.
Installing 2025.3.1 on a newer image won't work for libcamera ABI compat, and I don't think we should be really supporting inter year flashing anyways?
It doesn't hurt though, and it's a good idea to think about backwards-compat.
There was a problem hiding this comment.
Our images are still defaulting to 2025.3.1 because it's the latest release. Plus, libcamera is only a problem for RPi-based systems. Nothing stopping someone with an OPi from running 2025 on a newer image.
samfreund
force-pushed
the
versioning
branch
from
7b2016f to
4d7318c
Compare
3 participants
Closes #90