agentleFS
beeblockbeeblock/orkestrai/.agents/skills/orkestrai-release/SKILL.md

orkestrai-release

Skill27 starsChanged 12 days agoApache-2.0View on GitHub

Prepare, publish, recover, and audit Orkestrai desktop releases for macOS, Windows, and Linux. Use when asked to cut or publish a new Orkestrai version, retry a failed release, inspect the Release Desktop workflow, validate public installers or latest-*.yml feeds, or diagnose desktop auto-update delivery.

  • Reads credentials
  • Deletes or force-pushes
  • Commits and pushes

The file

Show its rules and text

We split this skill into the rules it gives an agent

26 rules. About 0 are common, 14 are distinctive, and 12 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 12

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the complete release from the beeblock/orkestrai repository and do not stop while required GitHub Actions jobs are active.

    line 8
  2. Very specific:

    Read the repository AGENTS.md and docs/releases.md before changing files.

    line 12
  3. Very specific:

    Never print, read, or request the value of RELEASES_TOKEN.

    line 14
  4. Distinctive:

    Treat a public release as immutable.

    line 15
  5. Distinctive:

    Keep the release draft until every platform and manifest passes validation.

    line 17
  6. Very specific:

    Never tag a release until preflight confirms all five Apple signing/notarization secrets exist.

    line 18
  7. Distinctive:

    Run builds and tests sequentially.

    line 19
  8. Very specific:

    Read .agents/skills/orkestrai-release/references/release-contract.md when checking artifacts, signing behavior, or failure recovery.

    line 21
  9. Very specific:

    Use SemVer. Use the exact version requested when valid.

    line 27
  10. Distinctive:

    Update both package files through npm:

    line 31
  11. Very specific:

    Add the version section to CHANGELOG.md in English.

    line 39
  12. Very specific:

    Add equivalent translated changelog entries, in the same position and structure, to src/lib/i18n/docs/pt-BR.ts, en.ts, and es.ts.

    line 40
  13. Distinctive:

    Update README.md, long-form docs, use cases, and onboarding tours when required by AGENTS.md.

    line 41
  14. Distinctive:

    Add every new UI string to all three Paraglide catalogs.

    line 42
  15. Very specific:

    Keep installer names compatible with scripts/validate-release-artifacts.mjs and the latest-*.yml URLs.

    line 43
  16. Very specific:

    add the same version and changes to the three localized changelog catalogs in sibling ../orkestra-site.

    line 47
  17. Very specific:

    commit and push the applicable companion repositories, then let preflight verify that they are clean and synchronized with origin/main.

    line 49
  18. Distinctive:

    Do not create the tag yet.

    line 56
  19. Distinctive:

    Run focused integrity tests first, then the full suite and production build:

    line 60
  20. Very specific:

    When native dependencies changed, also run npm run electron:rebuild.

    line 68
  21. Distinctive:

    Create an annotated tag only after preflight passes:

    line 78
  22. Distinctive:

    Read the failed step before changing code:

    line 96
  23. Distinctive:

    Use the job logs API when the overall run is still active.

    line 102
  24. Distinctive:

    If the release is already public in any applicable repository, stop source-changing recovery and create a new patch version.

    line 112
  25. Distinctive:

    After the workflow succeeds, run:

    line 116
  26. Distinctive:

    Do not claim macOS automatic replacement works for an unsigned build.

    line 127

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Orkestrai Release

Run the complete release from the beeblock/orkestrai repository and do not stop while required GitHub Actions jobs are active.

Guardrails

  • Read the repository AGENTS.md and docs/releases.md before changing files.
  • Preserve unrelated user changes. Never stage, rewrite, or delete them.
  • Never print, read, or request the value of RELEASES_TOKEN; only verify that the secret name exists.
  • Treat a public release as immutable. Never force-move its tag or replace its assets. Prepare a new patch version instead.
  • A failed, unpublished tag may be moved only after confirming that the public release is absent or still draft.
  • Keep the release draft until every platform and manifest passes validation.
  • Never tag a release until preflight confirms all five Apple signing/notarization secrets exist. The source repository must be public, except for the one-time 0.1.4 transition while its identical user-facing release is published to the public legacy feed.
  • Run builds and tests sequentially. Follow the disk cleanup rules in AGENTS.md.

Read .agents/skills/orkestrai-release/references/release-contract.md when checking artifacts, signing behavior, or failure recovery.

1. Inspect And Select The Version

Inspect the branch, remotes, worktree, latest tags, public releases, workflow, package version, and newest changelog section. Fetch before deciding the version.

Use SemVer. Use the exact version requested when valid; otherwise infer patch/minor/major from the shipped behavior and state the choice. Before editing, verify that v<version> is neither a public release nor an existing tag for a normal new release.

2. Prepare The Release Commit

Update both package files through npm:

npm version <version> --no-git-tag-version

In the same commit:

  • Add the version section to CHANGELOG.md in English. This is the exclusive source for public GitHub Release notes.
  • Add equivalent translated changelog entries, in the same position and structure, to src/lib/i18n/docs/pt-BR.ts, en.ts, and es.ts.
  • Update README.md, long-form docs, use cases, and onboarding tours when required by AGENTS.md.
  • Add every new UI string to all three Paraglide catalogs.
  • Keep installer names compatible with scripts/validate-release-artifacts.mjs and the latest-*.yml URLs.

Synchronize the companion repositories before tagging:

  • add the same version and changes to the three localized changelog catalogs in sibling ../orkestra-site;
  • for the one-time 0.1.4 feed transition, add/update the three localized changelogs and README guidance in sibling ../orkestrai-releases;
  • commit and push the applicable companion repositories, then let preflight verify that they are clean and synchronized with origin/main.

Normal releases publish in beeblock/orkestrai with the workflow's automatic GITHUB_TOKEN. Version 0.1.4 additionally publishes the exact same artifacts to beeblock/orkestrai-releases using RELEASES_TOKEN. Never delete the legacy repository or its 0.1.4 release because old installations use it to migrate.

Do not create the tag yet.

3. Verify Locally

Run focused integrity tests first, then the full suite and production build:

npm test -- --run tests/unit/docs-catalog.test.ts tests/unit/tours-catalog.test.ts tests/unit/release-artifacts.test.ts
npm test
npm run build

When native dependencies changed, also run npm run electron:rebuild. Run relevant e2e tests only against a stable production build and remove test-results/ afterward as required by AGENTS.md.

Review git diff --check, the complete diff, and the final status. Commit only release-related files and push main. Then run the deterministic gate:

bash .agents/skills/orkestrai-release/scripts/preflight.sh <version> new

4. Tag And Monitor

Create an annotated tag only after preflight passes:

git tag -a v<version> -m "Orkestrai v<version>"
git push origin v<version>

Find the Release Desktop run and monitor it through completion:

gh run list --repo beeblock/orkestrai --workflow "Release Desktop" --limit 3
gh run watch <run-id> --repo beeblock/orkestrai --exit-status

Confirm all five jobs: tag validation, signed/notarized macOS, Windows, Linux, and verified publication. The macOS verification must prove Developer ID authority, Team ID, Hardened Runtime, Gatekeeper acceptance, and a stapled notarization ticket. For 0.1.4, confirm both repositories expose identical assets. Do not report completion while the run is queued or in progress.

5. Recover A Failed Unpublished Release

Read the failed step before changing code:

gh run view <run-id> --repo beeblock/orkestrai --log-failed

Use the job logs API when the overall run is still active. Fix the root cause, update tests/docs when applicable, commit, and push main.

For a transient failure with unchanged source, rerun the workflow for the existing tag. For a source fix, first prove the public release is absent or draft, then run:

bash .agents/skills/orkestrai-release/scripts/preflight.sh <version> recover
git tag -fa v<version> -m "Orkestrai v<version>" HEAD
git push --force origin v<version>

If the release is already public in any applicable repository, stop source-changing recovery and create a new patch version. Never mutate the public version. A transient rerun with unchanged source may finish the other destination if the transition release was only partially published.

6. Audit The Public Release

After the workflow succeeds, run:

node .agents/skills/orkestrai-release/scripts/audit-release.mjs <version>

Also inspect the release notes and confirm the workflow tag resolves to the intended source commit. Report the release URL, run URL, version, asset count, supported architectures, signing limitation, commits, and verification results.

For 0.1.4, the audit script verifies the primary and legacy feeds. For later versions it verifies only beeblock/orkestrai.

Do not claim macOS automatic replacement works for an unsigned build. Unsigned macOS releases use the manual-download fallback; signed/notarized releases can update in place.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.