The open-source app everyone uses to manage agents at work
TypeScript acpxagent-orchestrationagent-skillsagentic-aiai-agentsai-engineeringai-governanceai-toolsautonomous-agentsclaudeclaude-codeclaude-skillscodexhermesllmmcpmulti-agentopenclawproject-managementworkflow-automation
fix: use origin for github release creation in actions
dotta528f836e7174
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 59e25cefc2..0b5983ccd1 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -12,7 +12,7 @@ on:type: stringdefault: masterstable_date:- description: Stable release date in UTC (YYYY-MM-DD). First stable that day is .0, then .1, and so on.+ description: Enter a UTC date in YYYY-MM-DD format, for example 2026-03-18. Do not enter a version string. The workflow will resolve that date to a stable version such as 2026.318.0, then 2026.318.1 for the next same-day stable.required: falsetype: stringdry_run:@@ -251,6 +251,7 @@ jobs:- name: Create GitHub Releaseenv:GH_TOKEN: ${{ github.token }}+ PUBLISH_REMOTE: originrun: |version="$(git tag --points-at HEAD | grep '^v' | head -1 | sed 's/^v//')"if [ -z "$version" ]; thendiff --git a/doc/RELEASE-AUTOMATION-SETUP.md b/doc/RELEASE-AUTOMATION-SETUP.mdindex 06f70536c1..d987a3162d 100644--- a/doc/RELEASE-AUTOMATION-SETUP.md+++ b/doc/RELEASE-AUTOMATION-SETUP.md@@ -222,7 +222,8 @@ After at least one good canary exists:3. open `Actions` -> `Release`4. run it with:- `source_ref`: the tested commit SHA or canary tag source commit- - `stable_date`: leave blank or set the intended UTC date+ - `stable_date`: leave blank or set the intended UTC date like `2026-03-18`+ do not enter a version like `2026.318.0`; the workflow computes that from the date- `dry_run`: `true`5. confirm the dry-run succeeds6. rerun with `dry_run: false`@@ -231,6 +232,11 @@ After at least one good canary exists:9. confirm git tag `vYYYY.MDD.P` exists10. confirm the GitHub Release was created+Implementation note:++- the GitHub Actions stable workflow calls `create-github-release.sh` with `PUBLISH_REMOTE=origin`+- local maintainer usage can still pass `PUBLISH_REMOTE=public-gh` explicitly when needed+## 13. Suggested Maintainer PolicyUse this policy going forward:diff --git a/doc/RELEASING.md b/doc/RELEASING.mdindex 35d2b50acd..61d094c4df 100644--- a/doc/RELEASING.md+++ b/doc/RELEASING.md@@ -77,22 +77,31 @@ npx paperclipai@canary onboard --data-dir "$(mktemp -d /tmp/paperclip-canary.XXXUse [`.github/workflows/release.yml`](../.github/workflows/release.yml) from the Actions tab with the manual `workflow_dispatch` inputs.+[Run the action here](https://github.com/paperclipai/paperclip/actions/workflows/release.yml)+Inputs:- `source_ref`- commit SHA, branch, or tag- `stable_date`- optional UTC date override in `YYYY-MM-DD`+ - enter a date like `2026-03-18`, not a version like `2026.318.0`- `dry_run`- preview only when trueBefore running stable:1. pick the canary commit or tag you trust-2. resolve the target stable version with `./scripts/release.sh stable --date YYYY-MM-DD --print-version`+2. resolve the target stable version with `./scripts/release.sh stable --date "$(date +%F)" --print-version`3. create or update `releases/vYYYY.MDD.P.md` on that source ref4. run the stable workflow from that source ref+Example:++- `source_ref`: `master`+- `stable_date`: `2026-03-18`+- resulting stable version: `2026.318.0`+The workflow:- re-verifies the exact source ref@@ -122,7 +131,7 @@ This is mainly for emergency/manual use. The normal path is the GitHub workflow.```bash./scripts/release.sh stablegit push public-gh refs/tags/vYYYY.MDD.P-./scripts/create-github-release.sh YYYY.MDD.P+PUBLISH_REMOTE=public-gh ./scripts/create-github-release.sh YYYY.MDD.P```## Stable Changelog Workflow@@ -217,7 +226,7 @@ This is a partial release. npm is already live.Do this immediately:1. push the missing tag-2. rerun `./scripts/create-github-release.sh YYYY.MDD.P`+2. rerun `PUBLISH_REMOTE=public-gh ./scripts/create-github-release.sh YYYY.MDD.P`3. verify the GitHub Release notes point at `releases/vYYYY.MDD.P.md`Do not republish the same version.diff --git a/scripts/create-github-release.sh b/scripts/create-github-release.shindex ca7ff8d118..40a030cdb4 100755--- a/scripts/create-github-release.sh+++ b/scripts/create-github-release.sh@@ -19,7 +19,8 @@ Examples:Notes:- Run this after pushing the stable tag.- - Defaults to git remote public-gh.+ - Resolves the git remote automatically.+ - In GitHub Actions, origin is used explicitly.- If the release already exists, this script updates its title and notes.EOF}@@ -54,7 +55,9 @@ fitag="v$version"notes_file="$REPO_ROOT/releases/${tag}.md"-PUBLISH_REMOTE="${PUBLISH_REMOTE:-public-gh}"+if [ "${GITHUB_ACTIONS:-}" = "true" ] && [ -z "${PUBLISH_REMOTE:-}" ] && git_remote_exists origin; then+ PUBLISH_REMOTE=origin+fiPUBLISH_REMOTE="$(resolve_release_remote)"if ! command -v gh >/dev/null 2>&1; thenecho "Error: gh CLI is required to create GitHub releases." >&2