github-featured / composiohq--composio

发布

0 发布 1,233 Git 标签

RSS 订阅源
  • @composio/cli@0.2.32-beta.284 57574e4f7c
    比较

    fix(cli): point CLI install URL at the next branch (#3758)

    frostbyte_neo 发布于 2026-07-06 20:31:48 +00:00

    The documented one-line CLI install command curls install.sh from the
    main
    branch:

    curl -fsSL https://raw.githubusercontent.com/ComposioHQ/composio/main/install.sh | bash

    But the repository's default branch is next and there is no main
    branch.
    raw.githubusercontent.com does not fall back to the default branch, so
    the
    documented command returns HTTP 404 and the install fails for anyone who
    copies
    it from INSTALL.md.

    This replaces the main branch segment with next in the
    raw.githubusercontent.com/ComposioHQ/composio/<branch>/install.sh URL
    at every
    documented occurrence, so the install one-liner resolves. It matches the
    next
    branch already used for the raw asset URL in README.md. install.sh
    itself
    needs no change: it downloads binaries from release assets, not from a
    branch raw
    URL.

    Fixes #

    Changes

    • INSTALL.md: update the 5 .../composio/main/install.sh URLs to
      .../composio/next/install.sh (One-line Install, Install specific
      version, and
      the Troubleshooting / manual-download / environment-variable examples).
    • .github/workflows/build-cli-binaries.yml: same main -> next
      update at the
      2 URLs inside the create-install-instructions job's heredoc, which
      regenerates
      INSTALL.md as a GitHub Release artifact, so the released copy carries
      the
      working URL too and stays consistent with the checked-in file.

    Type of change

    • Bug fix
    • New feature
    • Refactor/Chore
    • Documentation
    • Breaking change

    How Has This Been Tested?

    No application code changed (static Markdown plus a CI heredoc), so no
    unit test
    applies. Verified the branch/URL facts directly:

    # Default branch is next; no main branch exists
git ls-remote --symref origin HEAD          # -> ref: refs/heads/next
git ls-remote --heads origin main next      # only refs/heads/next (+ changeset-release/next); no main

# The broken vs working URL, live
curl -s -o /dev/null -w "%{http_code}" https://raw.githubusercontent.com/ComposioHQ/composio/main/install.sh   # 404
curl -s -o /dev/null -w "%{http_code}" https://raw.githubusercontent.com/ComposioHQ/composio/next/install.sh   # 200

# After the change: 0 remaining main URLs, 7 next URLs
grep -rn "composio/main/install.sh"  INSTALL.md .github/workflows/build-cli-binaries.yml   # no matches
grep -rn "composio/next/install.sh"  INSTALL.md .github/workflows/build-cli-binaries.yml   # 7 matches

# The workflow YAML still parses cleanly after the heredoc edit
python -c "import yaml; yaml.safe_load(open('.github/workflows/build-cli-binaries.yml'))"

    Screenshots (if applicable)

    N/A.

    Checklist

    • I have read the Code of Conduct and this PR adheres to it
    • I ran linters/tests locally and they passed
    • I updated documentation as needed
    • I added tests or explain why not applicable
    • I added a changeset if this change affects published packages

    Additional context

    The 14 github.com/ComposioHQ/composio/tree/main/... homepage fields
    in
    ts/**/package.json also point at the non-existent main branch, but
    those are
    published-package metadata (a different URL form that would require a
    changeset)
    and are left out to keep this PR single-purpose. They are a reasonable
    follow-up.

    下载附件