Populate version strings from CI#278
Conversation
|
@gokugiant when you have a chance, could you please try deploying the ImSwitch Docker container image at https://github.com/openUC2/ImSwitch/pkgs/container/imswitch/887509239?tag=sha-f23a2ce to your RPi, in order to check what version string is reported from that ImSwitch container's frontend? Currently I don't have any practical way of testing the functionality of this PR myself on an RPi (because the RPi at my desk in the office is still not accessible either via Tailscale or via the office LAN, and I don't have a sufficiently fast/stable internet connection for the RPi I have with me) - so if you can test it, this would be very helpful. Thanks! |
|
Here's a screenshot which @gokugiant sent me, confirming that the frontend reports the expected version strings: |
This PR automatically sets the backend and frontend's version strings from VCS information available during the build CI workflows, in order to remove the need to manually/automatically create VCS commits for updating version strings after changes are made. The version strings produced by this PR do not follow the pseudoversion format used in Go Modules or Forklift; instead, they look something like "v2.1.192-89-g930ffbe-t20260523153301-pr278" for PR commits and something like "v2.1.192-89-g930ffbe-t20260523153301" for non-PR commits. For builds of pushed tags, they should look like "v2.2.0" (but that functionality is not yet tested). This work is tracked on Notion at https://www.notion.so/Bake-VCS-info-into-the-ImSwitch-container-image-3574e612c78a8053929ce57897eee6c7?source=copy_link
This PR automatically sets the backend and frontend's version strings from VCS information available during the build CI workflows, in order to remove the need to manually/automatically create VCS commits for updating version strings after changes are made. The version strings produced by this PR do not follow the pseudoversion format used in Go Modules or Forklift; instead, they look something like "v2.1.192-89-g930ffbe-t20260523153301-pr278" for PR commits and something like "v2.1.192-89-g930ffbe-t20260523153301" for non-PR commits. For builds of pushed tags, they should look like "v2.2.0" (but that functionality is not yet tested). This work is tracked on Notion at https://www.notion.so/Bake-VCS-info-into-the-ImSwitch-container-image-3574e612c78a8053929ce57897eee6c7?source=copy_link
1 participant
This PR automatically sets the backend and frontend's version strings from VCS information available during the build CI workflows, in order to remove the need to manually/automatically create VCS commits for updating version strings after changes are made.
The version strings produced by this PR do not follow the pseudoversion format used in Go Modules or Forklift; instead, they look something like "v2.1.192-89-g930ffbe-t20260523153301-pr278" for PR commits and something like "v2.1.192-89-g930ffbe-t20260523153301" for non-PR commits. For builds of pushed tags, they should look like "v2.2.0" (but that functionality is not yet tested).
This work is tracked on Notion at https://www.notion.so/Bake-VCS-info-into-the-ImSwitch-container-image-3574e612c78a8053929ce57897eee6c7?source=copy_link