Question about latest version retrieval using github actions (no npm) and git-tags

[smoia]

I tried to setup auto in a python repository, without using npm - downloading the latest release from github - with this Github action.
From the last log of the action, the one before, and the first one after merging auto , it seems like auto retrieves the latest release correctly, but then:

• it seems like the labels are not set in the repository, when they are (I ran auto create-labels a couple of times to be sure)
• it seems like it uses the version before the last one to compute the new version
• it fails because the version it computed already exists.

Am I missing something in the configuration files?

[hipstersmoothie]

@smoia are you still experiencing these issues?

[smoia]

Hello @hipstersmoothie! Yes and no: Yes because when I call auto release I do have this issue, no because if I use auto shipit I don't. In fact, the set up is now working quite well (we release a couple of versions with it) - let's see if it will be ok with the move to v10!
If you want, you can add our action to the documentation as an example of GitHub action that is not using npm.

[hipstersmoothie]

@smoia I'd happily accept a PR for those changes. Let's get you on that contributor list 😉

[hipstersmoothie]

I think the problem stems from a misunderstanding:

• auto release - Creates a GitHub release for the last tag in the repo
• auto shipit - Will create the tag and call auto release

[smoia]

I see, and now that's clear, thank you! May I suggest a tiny change to the documentation in this case? Just to make 100% more clear the difference between shipit and release.

[hipstersmoothie]

Go for it!

[alinaMihai]

What would be a reason for the auto shipit not to add the latest label on the tag it created?
I have previously made a manual release from Github interface with a release tag. I am using an individually versioned configuration for lerna.