ci: stop Update README corrupting the plugin version lines (unblocks the 1.0.0 release)

[NickJosevski]

The problem

The 1.0.0 release PR (#13) has a failing Lint check, so the release is blocked. The cause is this workflow, not the release.

Update README rewrites the plugin version in the README's examples with:

sed -i "s/\(OctopusDeploy\/create-release#\).*/\1v${VERSION}/g" README.md

.* also consumes the trailing colon of the YAML mapping key:

-      - OctopusDeploy/create-release#v0.1.1:
+      - OctopusDeploy/create-release#v1.0.0

Every example then becomes an unkeyed sequence entry followed by indented mappings, and the plugin linter rejects it:

not ok 2 - bad indentation of a sequence entry (8:18)
   7 |       - OctopusDeploy/create-release#v1.0.0
   8 |           project: "HelloWorld"  ----^

This bug has been present since the workflow was added. It simply never ran — there has been no release since 2022, and update-readme only triggers on pushes to release-please--**.

The fix

-          sed -i "s/\(OctopusDeploy\/create-release#\).*/\1v${VERSION}/g" README.md
+          sed -i -E "s|(OctopusDeploy/create-release#)v?[0-9][^:[:space:]]*:?|\1v${VERSION}:|g" README.md

Matches only the version and always re-emits the colon. Two useful properties:

• Self-healing — it also repairs a README that a previous run already mangled, which matters because chore(main): release 1.0.0 #13's branch is currently in that state.
• Still scoped to create-release#, so other plugins' refs are untouched. The README now references OctopusDeploy/octopus-login#v1.0.0, which must keep its own version.

Also: a push race

release-please pushed to the release branch three times in quick succession, so three Update README runs started together and raced on git push. One failed:

! [rejected]  release-please--branches--main -> release-please--branches--main (fetch first)

Two of the three succeeded so the outcome was fine, but it's luck. Added a concurrency group keyed on the ref, with cancel-in-progress: false so the last push still gets applied rather than cancelled.

Verification

Ran the new sed over main's README and linted the result:

ok 1 - plugin.yml configuration is valid
ok 2 - All the readme config examples for plugin id 'OctopusDeploy/create-release' are valid (7 found)

Also confirmed the old sed reproduces #13's exact failure, and that the new one repairs #13's already-corrupted README.

After this merges

release-please will refresh #13's branch, Update README will re-run with the fixed sed, and Lint should go green — unblocking the 1.0.0 release. Worth a check rather than an assumption, since that workflow can only be exercised for real on a release branch.

🤖 Generated with Claude Code