Skip to content

Add the version pipeline and branch naming convention - #14

Merged
VidGuiCode merged 2 commits into
mainfrom
chore/workflow-docs
Oct 28, 2026
Merged

VidGuiCode merged 2 commits into
mainfrom
chore/workflow-docs

Conversation

@VidGuiCode

Copy link
Copy Markdown
Owner

What

  • Adds skills/version-pipeline/SKILL.md: the agent procedure for shipping a version (branch, PR, CI, merge, tag, publish).
  • Adds "How a version is released" and "Branch names" to CONTRIBUTING.md.
  • Adds the pipeline rule to AGENTS.md.
  • Fixes the stale release number in .github/ISSUE_TEMPLATE/bug_report.yml (1.4.0 to 1.13.0).

Why

The 1.13.0 cycle showed four gaps: a stale release claim in a public template, version literals copied by hand, CI jobs gated on a branch name, and no written rule for branches.

Conventions set

Branch Use
release/X.Y.Z-<description> work that ships in a version
chore/<description> repository work that owns no version
spike/<description> an experiment, never merged

Verification

Documentation only. No code, schema, or artifact change. CI runs the normal matrix.

The template said 1.4.0. Set both occurrences to 1.13.0.
Record one branch for each version, one pull request to main, and one tag
after a green merge.

Name branches release/X.Y.Z-<description> for work that ships,
chore/<description> for repository work that owns no version, and
spike/<description> for an experiment that is never merged.

The skill gives agents the procedure. CONTRIBUTING.md gives contributors the
same rule, and AGENTS.md makes it a standing rule.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-28T12:22:46.872669Z 77bbd42 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 77bbd42432

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +127 to +131
The tag starts the Release workflow. All 14 jobs must pass.

## Stage 9 — publish

- Create the draft release from the changelog section.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Create the draft release before waiting for the Release workflow

For a new version, this procedure waits for all Release jobs to pass before creating the release they need. In .github/workflows/release.yml, the attach job runs gh release upload "$TAG" dist/* --clobber, and the six verify jobs depend on it. The locally checked gh release upload --help describes uploading files “to a GitHub Release”; it does not create that release. A repository-wide search found no release-creation step or wrapper. Create the draft before the upload job runs, or add draft creation to the workflow; otherwise following this sequence blocks release acceptance.

Useful? React with 👍 / 👎.

Comment on lines +86 to +87
- Bump `Cargo.lock`, `ui/package.json`, `ui/package-lock.json`, and
`packaging/homebrew/assemblash.rb`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Defer the entire Homebrew formula update until hashes exist

When preparing the next version, this step bumps the formula before the new archive hashes exist. The formula contains literal versioned download URLs and four SHA-256 values, so updating its version strings while retaining the previous hashes makes installation fail checksum verification once the new archives are published. Stage 10 already provides a post-publication formula pull request. Move the complete formula update there so its version, URLs, and hashes change together.

Useful? React with 👍 / 👎.

@VidGuiCode
VidGuiCode merged commit 175f6d4 into main Oct 28, 2026
13 checks passed
@VidGuiCode
VidGuiCode deleted the chore/workflow-docs branch November 10, 2026 10:53
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.

1 participant