fix: incorrect image release tags in build

[johnson2427]

What I did

The tag that is created when merged to main is main. We want this to be latest and then on version release, we want this to be stable

fixes: APE-1769

How I did it

Added the tag to the build yaml

How to verify it

After merge, check the release

Checklist

• All changes are completed
  - [ ] New test cases have been added
  - [ ] Documentation has been updated

[antazoey]

I am guessing this is container-related?

[johnson2427]

I am guessing this is container-related?

yes it is, not getting the right tags on merge to main

[johnson2427]

These changes should do what we're looking for. I'm not familiar with tagging in github, so I'm riding on documentation, but still a little unclear on this

[fubuloubu]

Noticed that the untagged versions were getting pushed from this PR, did a597ba9 resolve that?

---

ref: https://github.com/ApeWorX/ape/pkgs/container/ape/261370690

[fubuloubu]

Also can you delete this?
https://github.com/orgs/ApeWorX/packages/container/ape/261405854?tag=main

[johnson2427]

Noticed that the untagged versions were getting pushed from this PR, did a597ba9 resolve that?

ref: https://github.com/ApeWorX/ape/pkgs/container/ape/261370690

I'm reviewing docs right now, this isn't supposed to push unless it's merged to main

[fubuloubu]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

[johnson2427]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

you don't want to release unless it's a tagged version? So don't release on merge to main?

[fubuloubu]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

you don't want to release unless it's a tagged version? So don't release on merge to main?

No no, those random untagged releases which are image hashes. Don't know where those come from

[johnson2427]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

you don't want to release unless it's a tagged version? So don't release on merge to main?

No no, those random untagged releases which are image hashes. Don't know where those come from

I think this is resolved. I don't see it in the package releases. And I'm no longer pushing until we merge to main. We should be okay here

[fubuloubu]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

you don't want to release unless it's a tagged version? So don't release on merge to main?

No no, those random untagged releases which are image hashes. Don't know where those come from

I think this is resolved. I don't see it in the package releases. And I'm no longer pushing until we merge to main. We should be okay here

So we can get this merged to see?

[johnson2427]

Lastly, would love it if the untagged versions didn't get published at all, feel like that bloats things

you don't want to release unless it's a tagged version? So don't release on merge to main?

No no, those random untagged releases which are image hashes. Don't know where those come from

I think this is resolved. I don't see it in the package releases. And I'm no longer pushing until we merge to main. We should be okay here

So we can get this merged to see?

we can merge now to see. We won't know for sure on the tagged release until we do a tagged version release

[johnson2427]

If this does not work, I'm removing the metadata step and forcefully injecting the tags