Releases: bradtaylorsf/alpha-loop
Releases · bradtaylorsf/alpha-loop
v2.2.0
v2.1.0
v2.0.5
v2.0.4
ci(release): break infinite-loop chain on auto-bump merges (#276)
The post-publish commit-back step creates a chore(release): bump version
to vX.Y.Z PR; merging that PR is a push to master, which triggers ANOTHER
release run, which publishes vX.Y.(Z+1) and creates ANOTHER bump-PR.
Repeats forever.
This adds a guard at the top of Determine version: if the latest commit
matches the bot's bump-back subject pattern, set skip=true and exit
before any version computation. The rest of the workflow short-circuits
via the existing 'if: steps.version.outputs.skip != true' guards.
Regex covers both the raw form ('chore(release): bump version to v2.0.3')
and the GitHub-squash-merge-decorated form ('... (#274)').
v2.0.3
chore(release): bump version to v2.0.2 (#274) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
v2.0.2
chore(release): sync package.json to v2.0.1 [post-release sync] (#273) The cfdb1680 release published v2.0.1 to npm but the post-publish commit-back step failed (GitHub Actions lacked permission to create PRs at the repo level). That permission is now flipped on, so future releases will auto-sync. This commit fixes the immediate mismatch: npm: 2.0.1 master: 2.0.0 (was) After merge, the release workflow will fire on master push and bump to 2.0.2 (chore prefix = patch bump), giving us a clean end-to-end validation of the now-fixed commit-back path.
v2.0.1
v2.0.0
feat!: release v2.0.0 — loop reliability cleanup, seeded harness skil…
v1.15.7
v1.15.6
Session: session/epic-243-epic-seeded-harness-skills-runner-setup-iss…