Skip to content

releases should publish new version tags #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
larhauga opened this issue Feb 17, 2025 · 5 comments
Closed

releases should publish new version tags #99

larhauga opened this issue Feb 17, 2025 · 5 comments

Comments

@larhauga
Copy link
Collaborator

Currently only the edge tag is updated.
New versions should create their own release specific tags in addition to the edge tag being updated.

I think that there is a limit on which tags the workflows are allowed to publish to, so that there is configuration on github in addition to the workflows that needs to be updated?

@anderseknert
Copy link
Member

Sounds very good to me!

Tbh, I'd prefer it if we pushed images only to GitHub for future releases, as it would simplify maintenance. WDYT?

For any release here, we need to remember to update the OPA docs on Docker too https://www.openpolicyagent.org/docs/latest/docker-authorization/

@larhauga
Copy link
Collaborator Author

Sounds very good to me!

Tbh, I'd prefer it if we pushed images only to GitHub for future releases, as it would simplify maintenance. WDYT?

For any release here, we need to remember to update the OPA docs on Docker too https://www.openpolicyagent.org/docs/latest/docker-authorization/

I agree. Its so much easier to only publish to ghcr.

@larhauga
Copy link
Collaborator Author

I see now that there has been published a tag named 'v0.9' last year, but never created a release for it. Since the tag already exists, the release workflow https://github.com/open-policy-agent/opa-docker-authz/blob/main/.github/workflows/release.yaml#L4-L7 was not run, resulting in no release specific images published.

@anderseknert should we create a new release, or tag the latest commit on main with v0.9 as we have released a v0.9 version now?

@anderseknert
Copy link
Member

I see both a v0.9 tag and release, but the automation probably didn't work for whatever reason, and I didn't have time to dig into why at the time.

Yeah, let's update the build to push only to ghcr and then tag v0.10, and build a release from that. Will you do the honors? 🙂 I can have the OPA docs updated once that's out.

@larhauga
Copy link
Collaborator Author

Release v0.10 is now published to seperate tags. Sorry for the delay :)
https://github.com/open-policy-agent/opa-docker-authz/pkgs/container/opa-docker-authz

PR for doc update: open-policy-agent/opa#7513

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants