---

This section details on the original issue you should resolve

<issue_title>Skip per-package monorepo release tags in container builds</issue_title>
<issue_description>## Summary

When used in a monorepo that generates per-package releases (e.g., via release-build-flow-action in monorepo mode), the container build flow fires once for every package release — not just the root/unified release. This results in multiple redundant container builds, broken image tags, and wasted CI minutes.

Current Behavior

1. A monorepo release workflow creates per-package GitHub Releases with tags like @tinyclaw/core@0.1.0, @tinyclaw/shell@0.1.0, etc.
2. A container workflow with on: release: types: [published] triggers for each of those releases.
3. detect-build-flow.sh sees GITHUB_EVENT_NAME=release and processes the per-package tag as if it's a standard semver release tag.
4. The @scope/name@version format doesn't match the expected semver pattern (v1.2.3), causing:
   • Failed semver parsing
   • Broken/invalid container image tags
   • Multiple redundant build attempts (one per package)

Expected Behavior

The action should be able to distinguish between:

• Root/unified release tags (e.g., v1.0.0) → build the container image
• Per-package monorepo tags (e.g., @scope/package@1.0.0, package@1.0.0) → skip the container build

Suggested Solution

Add a new input to control which release tags trigger a container build:

inputs:
  release-tag-pattern:
    description: 'Regex pattern to match release tags that should trigger container builds (default: matches semver with optional v prefix)'
    required: false
    default: '^v?[0-9]+\.[0-9]+\.[0-9]+'

In detect-build-flow.sh, add a check at the release detection stage:

elif [ "$GITHUB_EVENT_NAME" = "release" ]; then
    # Check if release tag matches the expected pattern
    if [[ -n "${RELEASE_TAG_PATTERN}" ]] && ! [[ "${RELEASE_TAG}" =~ ${RELEASE_TAG_PATTERN} ]]; then
        log_warning "Release tag '${RELEASE_TAG}' does not match pattern '${RELEASE_TAG_PATTERN}' - skipping build"
        flow_type="skip"
        # ... set outputs and exit early
    fi
    # ... existing release detection logic
fi

Alternatively (or additionally), the action could auto-detect monorepo-style tags by checking for @ in the tag name:

# Auto-skip per-package monorepo tags (e.g., @scope/pkg@1.0.0 or pkg@1.0.0)
if [[ "${RELEASE_TAG}" == *"@"* ]]; then
    log_info "Detected monorepo per-package tag, skipping container build"
    # ... exit gracefully
fi

Workaround

Currently, users must add a manual job condition in their workflow:

jobs:
  build:
    if: github.event_name != 'release' || startsWith(github.event.release.tag_name, 'v')

This works but is fragile and pushes the responsibility to consumers of the action.

Context

Discovered while using this action alongside release-build-flow-action (monorepo mode) in the tinyclaw project. The release action creates 20+ per-package releases, each triggering a container build workflow.

Related

• Skip private packages in monorepo release workflow release-build-flow-action#25 — Skip private packages in monorepo release workflow (source of the spurious releases)</issue_description>

Comments on the Issue (you are @copilot in this section)