Extract upload-action into a standalone repository for independent versioning

[BigLep]

Context

The upload-action currently lives at upload-action/ inside the filecoin-pin monorepo and is versioned alongside the CLI and library. Now that we are treating it as the authoritative GitHub Action for uploading to Filecoin — IP Shipyard is not taking on this work in ipfs-deploy-action (see ipshipyard/ipfs-deploy-action#39) — it needs to be independently releasable.

Per discussions with Rod (2026-05-26): extract into its own repo to avoid version lockstep between the npm package and the action, and to get cleaner issue tracking separation.

Why

1. Decouple release cadence. A docs-only or action-logic change shouldn't require a full filecoin-pin release, and a library release shouldn't force action consumers to update.
2. Follow GitHub Actions conventions. Actions are typically pinned with @v1 / @v1.2.3 on the action's own repo. Today consumers use filecoin-project/filecoin-pin/upload-action@v0 (subdirectory action in a monorepo), which works but is non-standard.
3. Independent issue tracking. Action-specific issues and PRs won't be interleaved with CLI/library work.
4. Future flexibility. A standalone action repo opens the door for independent evolution including potential monetization opportunities.

Proposed plan

• Create filecoin-project/filecoin-pin-upload-action (or similar) repo
• Move upload-action/ contents (action.yml, src/, examples/, FLOW.md) to the new repo
• Set up the new repo to install filecoin-pin from npm (already the case — the action runs npx filecoin-pin under the hood)
• Establish independent release-please / semantic versioning (target v1 for GA)
• Update references in filecoin-pin README, docs, and filecoin-pin-website to point to the new repo
• Add a deprecation notice or redirect in upload-action/ in the monorepo for a transition period

Pre-requisites

• GA: Upload action doc fixes #524 — GA upload action doc fixes (do first, before extraction)

Related

• Review/update API for GA #279 — GA tracking
• Add filecoin-pin support ipshipyard/ipfs-deploy-action#39 — original issue for filecoin-pin support in ipfs-deploy-action
• feat!: v2: deterministic CAR, composable pinning ipshipyard/ipfs-deploy-action#53 — IP Shipyard's recipe-based approach

[SgtPooki]

can we name it something like FilOzone/filecoin-pin-upload or FilOzone/gha-filecoin-pin-upload

[BigLep]

Triage comment from 2026 FOC Board Triage (Post GA): The sooner we do this, the sooner we can have release tags and proper gha versioning. this will give us more exposure to folks looking to replace fleek or other (if they haven't already moved on)

however, i don't believe this drives ARR, but it will drive word-of-mouth and number of customers, which we can potentially use to pull in bigger fish