4 Commits

Include renames

Author	SHA1	Message	Date
asepharyana	3c04aa44b6	fix(release): dispatch publish via gh api in exec successCmd ... gh workflow run failed inside successCmd (exit 1, no output shown). Switch to gh api REST dispatch which is transparent and reliable. successCmd only runs after semantic-release actually publishes a new version, so this fires once per release, exactly on the new tag. Remove the separate Detect step (it depended on git state that is not updated by semantic-release).	2026-08-28 17:15:12 +07:00
asepharyana	6c8c98e86c	fix(release): dispatch publish via exec successCmd not step output ... The prior pattern relying on steps.semantic-release.outputs did not fire. Move the publish dispatch into @semantic-release/exec successCmd, which runs only after a release is actually published and has nextRelease.version available. Also add GH_TOKEN env for gh CLI (GITHUB_TOKEN alone is not read by gh).	2026-08-28 17:10:16 +07:00
asepharyana	90322b5f97	fix(release): remove --locked from cargo check in release prepare ... cargo check --locked fails after bumping version in Cargo.toml because Cargo.lock needs to be regenerated with the new root package version. Semantic-release bump then committed Cargo.toml+CHANGELOG but lockfile stayed stale, so the whole prepare step errored out.	2026-08-28 17:06:51 +07:00
asepharyana	12a1ab10d0	feat(release): add semantic-release auto versioning ... - Add .releaserc.json: conventional commits -> semantic version bump (major/minor/patch), updates Cargo.toml + Cargo.lock version, writes CHANGELOG.md, commits as 'chore(release): X.Y.Z [skip ci]' - Add release.yml: runs semantic-release on main push, then triggers publish.yml via workflow_dispatch with the new tag - Update publish.yml: add workflow_dispatch input (tag) so release workflow can trigger publish directly (GITHUB_TOKEN tag pushes do not trigger 'on: push: tags'); still supports manual tag pushes	2026-08-28 17:03:12 +07:00