Releases: ipshipyard/ipfs-deploy-action
Releases · ipshipyard/ipfs-deploy-action
v1.10.0
Changed
- Updated actions (requires Actions Runner v2.327.1+ on self-hosted runners due to Node 24 runtime):
actions/upload-artifact@v4->actions/upload-artifact@v7actions/github-script@v7->actions/github-script@v8peter-evans/find-comment@v3->peter-evans/find-comment@v4peter-evans/create-or-update-comment@v4->peter-evans/create-or-update-comment@v5
v1.9.2
Fixed
- README: dual workflow example now documents
event == 'push'check for production deployment gates to prevent fork PRs from bypassing branch name conditions.
v1.9.1
Fixed
- Fix Storacha deprecation blog post URL in warning and docs.
v1.9.0
Changed
- Deprecate Storacha: uploads will stop working on April 15, 2026. A warning is now shown in CI run summary when Storacha credentials are configured. See Storacha announcement.
- Allow Filebase as a standalone CAR upload provider (no longer requires Kubo or IPFS Cluster alongside it).
v1.8.0
Changed
- Migrate from deprecated
@web3-storage/w3clito@storacha/cli. Existing workflows continue to work without changes.
v1.7.0
Fixed
- Add support for using ipfs-deploy-action in workflows triggered by
workflow_runevents to allow secure usage in PRs from forks.
v1.6.0
Added
- Add optional
github-status-gwinput to allow for customizing the gateway used for the commit status updates.
v1.5.0
Added
- Add
set-pr-commentinput to control PR comment creation separately from GitHub commit status
Fixed
- Fix bug where GitHub commit status was still being set when
set-github-statuswas set to 'false' - Update descriptions to clarify that string values 'true' and 'false' are expected for boolean inputs
v1.4.1
Fixed
- Fix commit status and PR comment when action is triggered by
pull_request_targetevent. - Fix bug in
ipfs-cluster-ctl-versioninput not being used correctly.
v1.4.0
Added
- Add support for time-bound pins in IPFS Cluster via the
cluster-pin-expire-ininput parameter. - Add support for custom pin names via the
pin-nameinput parameter.