You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now the mono-release-on-push action increments the version number of releases based on board type only.
This mostly works as intended e.g. if a new release is pushed to BoardA of PCB V1.1 with current release version 2.0.0 (BoardA-2.0.0-PCBv1.1) then the next release correctly becomes BoardA-2.1.0-PCBv1.1
However, if a patch is released for BoardA for a previous PCB version e.g. PCB V1.0 whose latest sw version was 1.0.0, then the mono-release-on-push will still increment the version number to BoardA-2.0.1-PCBv1.0 instead of BoardA-1.0.1-PCBv1.0 because it does not take the PCB version into account.
Unfortunately, the PCB version is not part of the tag of the release so there may be a need to do some search in the workflow prior to calling the mono-release-on-push action.
The text was updated successfully, but these errors were encountered:
As of now the
mono-release-on-push
action increments the version number of releases based on board type only.This mostly works as intended e.g. if a new release is pushed to BoardA of PCB V1.1 with current release version 2.0.0 (BoardA-2.0.0-PCBv1.1) then the next release correctly becomes BoardA-2.1.0-PCBv1.1
However, if a patch is released for BoardA for a previous PCB version e.g. PCB V1.0 whose latest sw version was 1.0.0, then the
mono-release-on-push
will still increment the version number to BoardA-2.0.1-PCBv1.0 instead of BoardA-1.0.1-PCBv1.0 because it does not take the PCB version into account.Unfortunately, the PCB version is not part of the tag of the release so there may be a need to do some search in the workflow prior to calling the
mono-release-on-push
action.The text was updated successfully, but these errors were encountered: