Skip to content

Add script for team sponsorship via squads import - #485

Open
metapileks wants to merge 1 commit into
developfrom
pileks/team-sponsor-squads
Open

Add script for team sponsorship via squads import#485
metapileks wants to merge 1 commit into
developfrom
pileks/team-sponsor-squads

Conversation

@metapileks

@metapileks metapileks commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Title

Greptile Summary

Adds an Anchor command that prepares a v0.6 team-sponsorship instruction for import into Squads.

  • Validates that the proposal belongs to the selected DAO.
  • Uses the DAO team address as the required signer and fee payer.
  • Prints the serialized transaction message in base58 and base64.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or independently actionable non-blocking issues identified.

The command follows established operator-script conventions, validates the DAO/proposal relationship, and intentionally emits an unsigned message for the external Squads signing workflow.

Important Files Changed

Filename Overview
Anchor.toml Registers the new sponsorship script under the v0.6 Anchor commands.
scripts/v0.6/sponsorProposal.ts Builds and exports a validated team-sponsorship transaction message for the external Squads signing workflow.

Reviews (1): Last reviewed commit: "team sponsor via squads script" | Re-trigger Greptile

@metapileks metapileks self-assigned this Aug 14, 2026
@metapileks
metapileks requested a review from metanallok as a code owner August 14, 2026 04:19
@github-actions

Copy link
Copy Markdown
Contributor

Repository Guard

  • Cargo.lock: pass
  • yarn.lock (root): pass
  • yarn.lock (sdk): pass
  • Repo guard: pass

Repository Guard

Cargo dependency pinning

  • Status: pass
  • Every programs/*/Cargo.toml dep uses =x.y.z, a path = .. workspace ref, or a git dep with a 40-char rev.

Cross-program Anchor/Solana version consistency

  • Status: pass
  • anchor-lang and anchor-spl are pinned to the version declared in repo-guard.toml across every program.

solana-program crate pin

  • Status: pass
  • Every solana-program = "=X" declaration is =1.17.14 (locked to match Cargo.lock).

Anchor.toml solana_version

  • Status: pass
  • Anchor.toml declares solana_version = "1.17.34" (local-dev install for anchor test).

Crate minimum age

  • Status: pass
  • All Cargo deps changed by this PR are at least 14 days old on crates.io.

Yarn package.json pinning

  • Status: pass
  • All package.json deps use exact versions (no ^, ~, ranges).

npm minimum age

  • Status: pass
  • All npm deps changed by this PR are at least 14 days old.

Workflow toolchain consistency

  • Status: pass
  • Every workflow declares anchor-version: 0.29.0.
  • Per-file solana-cli-version values match [toolchain.workflow_solana_cli] in repo-guard.toml.

GitHub Action SHA pinning

  • Status: pass
  • Every third-party action is pinned to a SHA in [actions.sha_allowlist].

Sensitive program / config changes

  • Status: warn
  • Review hint only (CODEOWNERS is the merge gate). Lines below match heuristics for security-sensitive changes:
  • High-sensitivity files touched: Anchor.toml

Overall status: pass

Lockfile freshness (Cargo.lock + yarn.lock) is checked by the workflow directly and cannot be bypassed. The sensitive-diff section is a review hint - CODEOWNERS handles the actual merge gate.

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