Skip to content

cd: automated release notes, binaries and man pages#21

Merged
jamesjohnsdev merged 2 commits into
mainfrom
dev
Jun 18, 2026
Merged

cd: automated release notes, binaries and man pages#21
jamesjohnsdev merged 2 commits into
mainfrom
dev

Conversation

@jamesjohnsdev

@jamesjohnsdev jamesjohnsdev commented Jun 18, 2026

Copy link
Copy Markdown
Owner
  • feat: add man page generation via cobra/doc
  • ci: automated releases with goreleaser and release-please

Summary by cubic

Automates releases and packaging with release-please and goreleaser, and adds man page generation for the issues CLI. Ships cross-platform binaries, a .deb, and man pages.

  • New Features
    • Man pages via cobra/doc; added tools/gen-man, make man, and make install-man (outputs to man/, gitignored; MANDIR defaults to /usr/local/share/man/man1); exposed cmd.Root() to enable docs.
    • Automated releases: release-please on main opens release PRs and tags; goreleaser on tags builds Linux/macOS/Windows (amd64/arm64; Windows amd64 only), publishes archives, checksums, and a Debian package.

Written for commit 9994d3e. Summary will update on new commits.

Review in cubic

Adds tools/gen-man and a Makefile with  and
targets. man/ is gitignored — generated at install time or in CI.
@jamesjohnsdev jamesjohnsdev changed the title cd: automated release notes and binaries cd: automated release notes, binaries and man pages Jun 18, 2026

@cubic-dev-ai cubic-dev-ai 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.

1 issue found across 11 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/release-please.yml">

<violation number="1" location=".github/workflows/release-please.yml:15">
P1: Release Please uses default `GITHUB_TOKEN`, which won't trigger the goreleaser workflow on tag pushes. Add a PAT or GitHub App token so the tag events fire downstream workflows.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread .github/workflows/release-please.yml Outdated
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@a02a34c4d625b9a4a434bd058532d5edecb6c70b # v4

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: Release Please uses default GITHUB_TOKEN, which won't trigger the goreleaser workflow on tag pushes. Add a PAT or GitHub App token so the tag events fire downstream workflows.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/release-please.yml, line 15:

<comment>Release Please uses default `GITHUB_TOKEN`, which won't trigger the goreleaser workflow on tag pushes. Add a PAT or GitHub App token so the tag events fire downstream workflows.</comment>

<file context>
@@ -0,0 +1,18 @@
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: googleapis/release-please-action@a02a34c4d625b9a4a434bd058532d5edecb6c70b # v4
+        with:
+          config-file: release-please-config.json
</file context>

- automatic release notes + tag generation
- automatic binary and .deb creation
@jamesjohnsdev jamesjohnsdev merged commit a85de8d into main Jun 18, 2026
7 checks passed
@jamesjohnsdev jamesjohnsdev deleted the dev branch June 18, 2026 03:54
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