-
Notifications
You must be signed in to change notification settings - Fork 281
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
Publish relay
, domain
, api
, web
images to ghcr.io
#5447
Labels
Comments
Hi @Intuinewin -- yes we discussed internally and moved away from portal/relay versioning because it would essentially be meaningless -- we don't follow semantic versioning there (there is only 1 version we run/support - I can look into adding a CI step to publish the images with the Git SHA like we do for our infra. |
relay
, domain
, api
, web
images to ghcr.io
jamilbk
added a commit
that referenced
this issue
Jun 24, 2024
It would be good to track the currently deployed SHA in production. refs #5447
This was referenced Jul 1, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 3, 2024
Fixes #5447 --------- Signed-off-by: Jamil <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hi, not really a feature request but a general question.
You recently split the versioning of clients, gateway and relay/portal components, but the release process of the last 2 components do not seem to appear in this refacto of the CI. I saw you deployed your production environment 2 days ago but no GH release or update of the containers in GHCR.
Are you still planning to do GH releases of portal components and relay?
And, if not, could you at least upload docker images to GHCR when you deploy your production environment?
The text was updated successfully, but these errors were encountered: