Skip to content

feat(release): each release publishes ncly-bin to the AUR #449

Open

Description

@pascalandy

This issue is the card COR-105-T2.

Problem

GoReleaser builds the ncly-bin AUR package, and just release-check checks it. But skip_upload: true in .goreleaser.yaml line 71 stops the upload. So Omarchy users cannot install ncly with yay.

Goal

Each nicely release publishes ncly-bin to the AUR.

Acceptance rules

  1. Before the change, the ssh check of chore(release): Pascal opens the AUR account for ncly-bin #448 answers from om1 with the key file that set the secret. Its fingerprint is equal to the fingerprint in chore(release): Pascal opens the AUR account for ncly-bin #448.
  2. .goreleaser.yaml has no skip_upload line in its aurs section, and no comment that says that the upload waits.
  3. Step 3 of the release-nicely skill says that the workflow publishes the AUR package.
  4. The card COR-105-T2 is done. The state of COR-105 starts with Shipped, COR-105 leaves the queue, and just test passes.
  5. The README gives yay -S ncly-bin as the install command on Arch Linux and Omarchy.

Examples

  • Success: after the next release, yay -S ncly-bin on om1 installs that version, and ncly <Tab> completes in bash.
  • Failure: the release workflow fails at the AUR step, or the AUR page shows an older version.

Check

The release workflow passes. On om1, ncly --version after yay -S ncly-bin prints the version of that release.

by Opus-5.5 via Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    1-ready-for-agentValidated work, sufficiently specified for an autonomous agent2-type:featureNew or improved functionality; specification lives in the issue3-pty:p2Normal planned work; default when no priority is established

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions