chore(release): version packages for v0.0.39 - #165
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
vouch:trusted
Greptile SummarySummaryThe release workflow can skip publishing a stable version when that version bump and a later watched-manifest change are pushed together. This must be corrected before merging. Confidence Score: 3/5Not safe to merge until the release workflow compares against the full pushed range. A reproduced release failure remains in the updated workflow: a multi-commit push can contain a stable version increment, yet publication is suppressed because the workflow compares the tip only with its immediate parent. Files Needing Attention: .github/workflows/release.yml
 T-Rex LogsWhat T-Rex did
|
Keep the generated version pull request body current after Tegami updates its branch, and dispatch the required repository checks explicitly. Skip stable release builds for ordinary manifest edits while rejecting reused release tags.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| if test "$EVENT_NAME" != workflow_dispatch; then | ||
| previous_version="$(git show "HEAD^:apps/server/package.json" | node -e "let data=''; process.stdin.on('data', chunk => data += chunk).on('end', () => console.log(JSON.parse(data).version))")" | ||
| for manifest in apps/desktop/package.json apps/web/package.json packages/contracts/package.json; do | ||
| previous="$(git show "HEAD^:$manifest" | node -e "let data=''; process.stdin.on('data', chunk => data += chunk).on('end', () => console.log(JSON.parse(data).version))")" | ||
| if test "$previous" != "$previous_version"; then | ||
| printf 'Previous package versions were not synchronized.\n' >&2 | ||
| exit 1 | ||
| fi | ||
| done | ||
| if test "$previous_version" = "$version"; then | ||
| printf 'publish=false\n' >> "$GITHUB_OUTPUT" | ||
| printf 'Stable version did not change; this push is not a release.\n' |
There was a problem hiding this comment.
If a push contains a version-bump commit followed by another change to a watched manifest, HEAD^ is the version-bump commit rather than the repository state before the push. The preflight then sees the same version at HEAD^ and at the pushed tip, writes publish=false, and skips publishing the new stable release. Read the prior manifests from the push event’s before SHA so the comparison covers every commit in the push.
Artifacts
- The executable script creates the bare remote and runs one- and two-commit push scenarios against the release preflight decision logic, ending with the demonstrated parent-versus-push-range distinction.
- The executed script output records the control release decision and the two-commit push that triggers the workflow path filter but writes publish=false, establishing the finding.
- The captured command record includes the exact executable script and its actual output with command, working directory, and exit code, ending with a successful reproduction.
leoisadev1
changed the title
1 participant
Summary
Prepare Akeru Bot v0.0.39.
Changes
Packages
@t3tools/desktop:0.0.38→0.0.39akeru-bot:0.0.38→0.0.39@t3tools/web:0.0.38→0.0.39@t3tools/contracts:0.0.38→0.0.39Release automation