Skip to content

Feature/ghcr container - #90

Merged
kk7ds merged 3 commits into
kk7ds:masterfrom
chrodriguez:feature/ghcr-container
Mar 6, 2026
Merged

kk7ds merged 3 commits into
kk7ds:masterfrom
chrodriguez:feature/ghcr-container

Conversation

@chrodriguez

Copy link
Copy Markdown
Contributor

Change docker-compose and update dockerfile using python 3. Also write a new gh action that publish container image into ghcr.io. Releases are named v*, If this is not wanted, I can change release number without v prefix.

Update docker image python version and add a GH Action to build and
publish into ghcr.io a new image on every commit or release
@kk7ds

kk7ds commented Mar 6, 2026

Copy link
Copy Markdown
Owner

Sorry for the delay. This looks okay to me I guess - looks like I just push a tag starting with v and it should push out a container image yeah?

@kk7ds
kk7ds merged commit 0d11aad into kk7ds:master Mar 6, 2026
1 check passed
@chrodriguez

chrodriguez commented Mar 7, 2026 •

Copy link
Copy Markdown
Contributor Author

It will push images to ghcr.io when:

  • You push into master branch, and if it's the default branch i will push an image using commit sha, and mark it as latest image
  • When using a tag, and tag version is prefixed with v, a new image will be pushed using semver tag

Here you can see generated images

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

Successfully merging this pull request may close these issues.

2 participants