Installed version number is different than what I requested

[vrou]

I have just installed the integration the other day, and found that the installed version differs from the expected version I chose when installing the integration in HACS.

This is the version number (3.4.2) shown in HACS:

This is the version number of the integration itself after being installed:

Maybe it's just a typo in the code, but how can I make sure that it is the newest version I have?

I also tried to remove to reinstall specifying the 3.4.2 version, but it still shows version 3.3.2.

[valimaties]

This is because manifest file have 3.3.2 set as the version number.

[RobHofmann]

Right. I'm thinking of setting this to 0.0.0; it's stupid to maintain two versions (which obviously always gets forgotten).

[valimaties]

I don't think this is a problem, however, if you want, you can implement a Github action to do that, something like this:

on:
  push:
    tags:
      - 'v*'

jobs:
  bump-version:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Update manifest version
        run: |
          VERSION=${GITHUB_REF#refs/tags/v}
          jq ".version = \"$VERSION\"" custom_components/gree/manifest.json > tmp.json
          mv tmp.json custom_components/gree/manifest.json
      - name: Commit changes
        run: |
          git config user.name "github-actions"
          git config user.email "actions@github.com"
          git add .
          git commit -m "Auto bump version to $VERSION"
          git push

Edit: This is an AI generated script, may be not accurate, but I posted it as an idea of implementation.

Setting the version to a "ghost" 0.0.0 version will be annoying for any user which will open integration in HA. Always will see 0.0.0, no matter HACS version will be. So, it is better to search a solution to automatically increment in project based on github tag. (I think 🤔)

Cheers

[p-monteiro]

I think both should exist and match up. If there is a way to automate it, better.

[vrou]

Whatever works :) Its just nice to know that its not a bug.