[M8.2d] Release tooling for agent and CLI

Open
  • Is something wrong?
#238 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, go
Domain
devops, release

Research direction

Start with .goreleaser.yaml and the release.yml workflow; first check the CI-1 dependency (#137) and whether the owner's Homebrew tap and Scoop bucket repositories are available. The task is done when a workflow_dispatch dry run produces signed artifacts for each platform and configures the agent and CLI release channels.

Written by the indexing model from the issue text.

Description

blocked priority:P2 task track:cross-cutting
Task id

M8.2d

Track

X: cross-cutting

Scope
  • .goreleaser.yaml for agent and CLI; Homebrew tap and Scoop bucket; first release.yml dry run via workflow_dispatch.
Acceptance criteria

A dry run produces signed artifacts for each platform.

Depends on

M3.5

Blocked by

CI-1 (#137) and the owner's tap and bucket repositories.

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.