My application stack is following:

• NextJS
• Docker (docker compose)
• GitHub Actions for CI/CD

I have following questions:

When is the best time and location to bump the version of the application?

What to use for tagging a docker image? Versioning semantics or commit hash?

Is it better to manually bump the version before merging pull request or automate it with github actions during CI step on the main branch?

My application stack is following:

• NextJS
• Docker (docker compose)
• GitHub Actions for CI/CD

I have following questions:

When is the best time and location to bump the version of the application?

What to use for tagging a docker image? Versioning semantics or commit hash?

Is it better to manually bump the version before merging pull request or automate it with github actions during CI step on the main branch?

• npm
• docker-compose
• version-control
• github-actions

1 Answer 1

For version bumping, the best time is usually before merging a PR if you want control over it, or automated in CI/CD if you prefer consistency. If you automate, bump it in the main branch during CI after merging.

For Docker image tagging, both versioning semantics and commit hash are useful.

If your workflow involves frequent releases, automating version bumps in GitHub Actions can work. But for strict control, manual bumping before merging works too.

Hope this helps!