[earakely-scale]

Why. Since #328, CircleCI hasn't run on main. Its CodeArtifact upload matches a 409 with grep -q "HTTPError: 409" <<<"$out", and CircleCI reads << as the start of a pipeline parameter, so the config doesn't compile. Without a pipeline there's no version bump, tag or release: #328 and #325 are both unreleased.

Change. The 409 check is [[ $out == *"HTTPError: 409"* ]]: the same match, without a <<. The step runs in bash.

Verified. circleci config validate (CLI 1.11.0):

• the config before fix(ci): publish to CodeArtifact without twine's PyPI-only --skip-existing #328: valid;
• main's config: contains compilation errors, pointing at the <<<;
• this branch's config: valid.

Labelled bump-version, so merging it cuts the next release with #328 and #325. That release's publish is the first run of #328's CodeArtifact upload since 0.9.1353, when it started failing.

🤖 Generated with Claude Code

Confidence Score: 5/5

This change appears safe to merge.

Summary

Replaces the here-string check in .circleci/config.yml with a Bash substring match.

• CircleCI can compile the CodeArtifact publish step and recognize existing files.

_{Reviews (1) · Last reviewed commit: "fix(ci): match the 409 without a here-st..." · Reviewed by Greptile}