tada5hi/action-docker-image-publish

GitHub action, to build, tag and push docker images.

action-docker-image-publish 🎍

This repository contains a GitHub action, to build, tag and push docker images, under certain conditions.

Usage

uses: tada5hi/action-docker-image-publish@v3
with:
    # Name of Dockerfile
    # Default: Dockerfile
    dockerFileName: 'Dockerfile'

    # Relative path to DockerFile
    # Default: ''
    dockerFilePath: ''
    
    # Whether to create an image tag for a git tag
    # Default: true
    gitTag: 'true'

    # Prefix for matching git tags
    # Default: ''
    gitTagPrefix: ''

    # Default: ghcr.io
    registryHost: 'ghcr.io'
    
    # Default: github.actor
    registryUser: ${{ github.actor }}
    
    # Default: ${{ github.token }}
    registryPassword: ${{ github.token }}

    # Registry repository full name (e.g. project/repository)
    # Default: github.repository
    registryRepository: ${{ github.repository }}

    # Registry image tag (e.g. latest)
    # Default: 'latest'
    registryTag: 'latest'

    # Delete the built image at the end
    # Default: 'true'
    cleanup: 'true'

action-docker-image-publish's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Bug: Patch Versions

Patch versions are not detected, and therefore not release as latest image tag.