Skip to content

Releases: bradtaylorsf/alpha-loop

v2.2.0

31 May 02:48
6246d5d

Choose a tag to compare

  • chore(release): release v2.2.0
  • feat: add targeted single-issue execution
  • chore: add project vision and context for alpha-loop

v2.1.0

28 May 03:29
b65011a

Choose a tag to compare

  • chore(release): release v2.1.0
  • feat: seed context rot skill and release hotfixes
  • added the agents skills
  • fix(release-watch): fetch tags so version-sync check sees the new tag (#282)

v2.0.5

27 May 02:56
a78efef

Choose a tag to compare

  • chore(release): release v2.0.5 (#281)
  • chore(release): bump version to v2.0.4 (#278)
  • chore(release): bump version to v2.0.3 (#275)

v2.0.4

26 May 22:21
ddb9de0

Choose a tag to compare

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

26 May 22:19
fc5e93e

Choose a tag to compare

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

26 May 22:11
4f8b23d

Choose a tag to compare

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

26 May 22:02
cfdb168

Choose a tag to compare

  • ci(release): fix permissions + drop --admin for commit-back step (#271)
  • chore: sync package.json to v2.0.0 + fix release workflow commit-back (#270)

v2.0.0

26 May 21:40
aee6f1a

Choose a tag to compare

feat!: release v2.0.0 — loop reliability cleanup, seeded harness skil…

v1.15.7

26 May 17:18
076c822

Choose a tag to compare

  • Session: session/epic-244-epic-sync-scan-safety-cli-observability-cleanup — 4/4 succeeded (#251)

v1.15.6

26 May 06:37
3b2dd7a

Choose a tag to compare

Session: session/epic-243-epic-seeded-harness-skills-runner-setup-iss…