Skip to content

Repo move: point npm, NuGet and release metadata at github/squad #2406

Closed

Description

@tamirdresher

The repo moved from bradygaster/squad to github/squad. Package and release metadata still names the old owner.

Broken

  • squad-npm-publish.yml publishes with --provenance. npm rejects a provenance publish when package.json repository.url doesn't match the source repository, and all three published manifests still point at bradygaster/squad.
  • NuGet Trusted Publishing for squad-agents-ai-release.yml is still bound to owner bradygaster on nuget.org.

Stale (works only through redirects)

  • Squad.Agents.AI project and repository URLs.
  • scripts/install.sh and scripts/generate-packaging.mjs defaults.
  • The WinGet DocumentUrl. The old docs host now returns 404.
  • Hardcoded release links in the standalone release workflow.

Needs a maintainer

  • On nuget.org, add a Trusted Publishing policy: Owner github, Repository squad, Workflow squad-agents-ai-release.yml, no environment. Then retire the bradygaster policy.

These stay on purpose: the npm scope @bradygaster/*, the WinGet IDs bradygaster.Squad*, and the Homebrew tap bradygaster/homebrew-squad, which didn't move.

Activity

  1. added a commit that references this issue on Nov 8, 2026
    180cbe4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions