Checked out 2.7.17, but builds 2.7.18

[lisachev]

Hi

I'm using GitHub actions/checkout@v4 to checkout 2.7.17 based on the release tag. Confirmed that it checked out the correct version in HEAD.

I then continue to build the checked out version with my custom build flags, but it ends up with a 2.7.18 build. Is there something wrong with my actions configuration or is there something wrong on the repo side?

      - name: Checkout firmware at exact release tag
        uses: actions/checkout@v4
        with:
          repository: meshtastic/firmware
          ref: ${{ steps.get_release.outputs.tag }}
          fetch-depth: 0
          submodules: 'recursive'
          path: firmware
      
      - name: Verify checkout
        run: |
          echo "Requested tag: ${{ steps.get_release.outputs.tag }}"
          git --no-pager show -s --format='HEAD=%H%nREFS=%D' HEAD
          echo "git describe: $(git describe --tags --long --always || true)"
          echo "Tags pointing at HEAD:"
          git tag --points-at HEAD || true
          echo "Submodule status:"
          git submodule status --recursive || true

[Xaositek]

Might have grabbed it sometime in the hot fix of 2.7.17; as of today it should be .17 in master and .18 in develop