Skip to content
This repository was archived by the owner on Jul 23, 2025. It is now read-only.

Conversation

@danbarr
Copy link
Collaborator

@danbarr danbarr commented Jan 6, 2025

Adds a note about versioning of the container image moving forward.

Ref stacklok/codegate#470 (comment)

@vercel
Copy link

vercel bot commented Jan 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
codegate-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 7, 2025 6:10pm

@danbarr
Copy link
Collaborator Author

danbarr commented Jan 6, 2025

@lukehinds I added a note to the changelog about the move to semver releases of the container image. I also mentioned we still recommend pulling latest, do you concur?


- **Semantic versioning for container image** - 29 Dec, 2024\
CodeGate is now using semantic versioning for the container image, tied to
GitHub releases. We'll continue to highlight major features and changes here,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, interesting, how do I view the tags? I tried:

skopeo list-tags docker://ghcr.io/stacklok/codegate

but I only see tags like 0.20250103.95-ref.8b95d7f

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I may have jumped the gun here - I was going off @lukehinds' post on Discord and here but looks like the actual image tags aren't wired up to the GitHub releases yet?

@danbarr danbarr marked this pull request as draft January 7, 2025 18:08
@danbarr
Copy link
Collaborator Author

danbarr commented Jan 7, 2025

Closing; not implemented (yet)

@danbarr danbarr closed this Jan 7, 2025
@danbarr danbarr deleted the image-semver branch January 7, 2025 21:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants