Repository navigation
Conversation
Trigger the Docker publish workflow on pushes to the dev branch (direct commits and PR merges). Each build is tagged with the moving `dev` tag and an immutable `dev-<short sha>` tag; `latest` is now gated to tag refs so a dev build can never reach prod via Watchtower. A per-ref concurrency group cancels superseded dev builds so a stale build cannot overwrite `dev`. Document the `dev` image in the getting-started guide. Assisted-by: ClaudeCode:claude-opus-5-5
Add a workflow that runs a pinned actionlint (with shellcheck for run blocks) on pushes and PRs to main/dev that touch .github/workflows. Assisted-by: ClaudeCode:claude-opus-5-5
Pushes to main now build the image and tag it `latest` plus an immutable `main-<short sha>`, so prod (Watchtower on `latest`) follows main without waiting for a version tag. Version tags keep their existing tagging. Superseded builds on any branch are cancelled so `latest`/`dev` can't be overwritten by a stale build. Assisted-by: ClaudeCode:claude-opus-5-5
dev Docker image on every push to devdev/latest Docker images on every push, lint workflows with actionlint
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #90 +/- ##
======================================
Coverage ? 83.35%
======================================
Files ? 21
Lines ? 3406
Branches ? 0
======================================
Hits ? 2839
Misses ? 567
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 AI text below 🤖
Summary
docker-publish.ymlnow also builds on pushes todevandmain(direct commits and PR merges):devdev(moving) +dev-<short sha>(immutable)mainlatest(moving) +main-<short sha>(immutable)v*tag / release<tag>, pluslatestfor non-prereleases (unchanged)latestvia Watchtower, so every merge tomainnow deploys right away instead of waiting for av*tag.latestfrommain. Adevbuild never touches it.concurrencygroup: a newer build on the same branch cancels the older one, so a stale build can't finish last and overwritedev/latest. Tag/release builds are never cancelled.actionlint.ymlworkflow runs a pinned actionlint (v1.7.12, with shellcheck forrun:blocks) on pushes/PRs tomain/devthat touch.github/workflows/**. It passes on this PR.docs/getting-started.mdnow documents thedevandlatestimages.Test plan
dev: GHCR showsdevanddev-<sha>, andlatestis unchangedmain: GHCR showslatestandmain-<sha>v*tag still publishes<tag>(+latestfor non-prereleases)🤖 Generated with Claude Code