Skip to content

fix(#325): release workflow rewrite + roadmap + cleanup#326

Merged
ajianaz merged 1 commit into
developfrom
fix/main-sync-and-docs
Jun 14, 2026
Merged

fix(#325): release workflow rewrite + roadmap + cleanup#326
ajianaz merged 1 commit into
developfrom
fix/main-sync-and-docs

Conversation

@ajianaz

@ajianaz ajianaz commented Jun 14, 2026

Copy link
Copy Markdown
Collaborator

Closes #325

Changes

Release workflow (.github/workflows/release.yml)

  • sync-main blocking again β€” removed continue-on-error, build-release and publish-crates now needs: [sync-main]
  • Safe fast-forward β€” checks merge-base --is-ancestor before pushing. If main diverged, aborts with error instead of blind force-push
  • No more separate develop checkout β€” sync-main checks out tag commit directly (tag already points to develop HEAD)

Roadmap (docs/roadmap.md)

Docs cleanup

  • docs/launch/: ajianaz β†’ codecoradev (3 files)
  • docs/architecture.md: model path models/embeddinggemma/ β†’ embeddinggemma-q4/onnx/
  • CHANGELOG.md: historical website URL updated

Root cause of #325

Commit 20cb3e8 made sync-main continue-on-error: true, so when it failed (main diverged from develop), builds proceeded anyway. The workflow fix makes sync-main blocking again β€” if main can't be fast-forwarded, the release aborts.

Post-merge action

After this PR merges to develop, main needs to be fast-forwarded to develop HEAD. The next v* tag push will auto-sync via the new workflow.

…refs (#325)

Release workflow:
- sync-main now tries fast-forward first, falls back to API force-update
- sync-main is blocking again (removed continue-on-error)
- build-release needs sync-main (was unblocked β€” root cause of #325)
- Checkout uses tag commit directly (no ref: develop needed)

Roadmap:
- Added v0.0.13/14/15 sections (were missing)
- Replaced speculative 'What's Next' with concrete v0.2.0 section
- Consolidated older versions for readability

Docs:
- Fixed ajianaz β†’ codecoradev in docs/launch/ posts
- Fixed model path in architecture.md (models/embeddinggemma/ β†’ embeddinggemma-q4/)
- Fixed CHANGELOG historical website URL
}
# The tag points to a commit on develop. We want main to point
# to the exact same commit so install.sh (which fetches from main)
# always matches the release binary.
@github-actions

Copy link
Copy Markdown

πŸ” Cora AI Code Review

❌ Blocked β€” critical issues found.

πŸ”΄ Error (1)

  • .github/workflows/release.yml:33 β€” The new sync-main logic changed behavior from force-updating main to hard-failing when origin/main is not an ancestor of TAG_SHA:
if git merge-base --is-ancestor origin/main "$TAG_SHA" ...; then
  git push origin "$TAG_SHA:refs/heads/main"
else
  ...
  exit 1
fi

The surrounding comments still state that main is a release-only mirror and that releases are triggered from tag pushes. In that workflow, a stale hotfix commit or any accidental divergence on main will now block the entire release, including build-release and publish-crates because both now need sync-main. This is a functional regression from the previous workflow, which explicitly handled divergence by force-updating the ref via the GitHub API.


Review powered by cora-cli Β· BYOK Β· MIT

@ajianaz
ajianaz merged commit 726dd32 into develop Jun 14, 2026
8 of 9 checks passed
@ajianaz
ajianaz deleted the fix/main-sync-and-docs branch June 14, 2026 02:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants