Tag version doesn't match the current version

[ps2goat]

0.1.0 is marked as latest. Shouldn't this be updated to 0.2.4?

[AlexanderMann]

@ps2goat, where are you seeing v0.1.0 being latest? You are correct everything should be v0.2.4 now.

[ps2goat]

On the main page, under "releases"

Also on the release description page for 0.1.0
https://github.com/datamill-co/target-postgres/releases/tag/v0.1.0

[ps2goat]

This caused me to have to specify a version when pulling so I could get 0.2.4, otherwise it would pull 0.1.0.

[AlexanderMann]

Ah, I see. Yeah, we're not presently "using" the releases feature. I think GH auto-enabled that for us long ago and we've just ignored it.

@ps2goat would a better request here be to:

• enable releases and support them properly
• turn off entirely releases to avoid confusion

❓

[ps2goat]

I think I looked at the release and tried to install the exact "latest" version using the version number. I see the py-pi badge, now, so maybe the best solution is to remove the github version of releases. (The latest tagging, anyway-- I like the change history.)

I'm usually on GH for the npm module repos, which usually rely on the release functionality. Sorry for the confusion!