Packer: Please mark packer tag v1.5.4 (and more) as "release" tag on github

Created on 19 Mar 2020  ·  4Comments  ·  Source: hashicorp/packer

Latest packer release on github is outdated tag v1.5.0

bug

Most helpful comment

Ah again ! There we go, thanks for reporting, again, I made it latest; this is weird.
We are currently planning on automating our release process so hopefully this is solved soonish 🙂

All 4 comments

Hello there, solved: https://github.com/hashicorp/packer/releases/tag/v1.5.4 thanks !

I just had to edit the release and save ( there's no option to tag as latest )

I think this used to be automagic 🤔

This issue reproduced again with release v1.5.5, which has not been marked as "release" on github and keeps treated as a non-release git tag by github (see https://github.com/hashicorp/packer/releases). You need to add a step in your release pipeline that marks a tag in github git as "released" tag.

Ah again ! There we go, thanks for reporting, again, I made it latest; this is weird.
We are currently planning on automating our release process so hopefully this is solved soonish 🙂

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

Was this page helpful?
0 / 5 - 0 ratings