Skip to content

feat(packaging): publish sayit-bin to OPR (script + npm command) - #12

Merged
ildella merged 1 commit into
masterfrom
feat/publish-omarchy
Oct 5, 2026
Merged

ildella merged 1 commit into
masterfrom
feat/publish-omarchy

Conversation

@ildella

@ildella ildella commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Implements the OPR publishing flow (OSP-16).

What

scripts/publish-omarchy.sh [--check] [version] (also npm run publish:omarchy):

  1. Requires release v<version> and asset SayIt_<version>_amd64.deb.
  2. Pulls the sha256 from the release API digest, downloads the asset anonymously with curl, checks the !<arch> magic and that the sha256 matches.
  3. Renders packaging/omarchy/sayit-bin/ (version + sha) into a clone of the OPR fork at ~/.cache/sayit/omarchy-pkgs, branch add-sayit-bin cut from upstream/master (omacom/omarchy-pkgs).
  4. Commits sayit-bin <version> and force-with-lease pushes that branch to the fork only; never writes to omacom.
  5. Writes the PR body to ~/.cache/sayit/omarchy-pkgs/sayit-bin-pr-body.md.

--check does the verification and render but stops before any clone write, commit or push.

Env overrides: OMARCHY_FORK_DIR, OMARCHY_FORK, OMARCHY_UPSTREAM, OMARCHY_PKGS_BRANCH.

Docs

packaging/omarchy/README.md gains a Publish section describing the script and the --check mode.

Refs OSP-16.

@ildella
ildella merged commit 0f93675 into master Oct 5, 2026
1 check passed
@ildella
ildella deleted the feat/publish-omarchy branch October 5, 2026 14:59
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