# Introducing a modern GitHub Action for deploying sites to IPFS - Built for 2025

**URL:** <https://discuss.ipfs.tech/t/introducing-a-modern-github-action-for-deploying-sites-to-ipfs-built-for-2025/19007>\
**Category:** Uncategorized\
**Created:** [February 17, 2025, 9:46am UTC](https://discuss.ipfs.tech/t/introducing-a-modern-github-action-for-deploying-sites-to-ipfs-built-for-2025/19007 "2025-02-17T09:46:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [February 17, 2025, 9:46am UTC](https://discuss.ipfs.tech/t/introducing-a-modern-github-action-for-deploying-sites-to-ipfs-built-for-2025/19007/1 "2025-02-17T09:46:29Z")

</div>

Hey folks,

I wanted to share a GitHub Action we’ve been working on over at [Shipyard](https://ipshipyard.com/) that makes deploying static sites to IPFS a breeze.

It implements all the current best practices for IPFS deployments in 2025.

> **[GitHub - ipshipyard/ipfs-deploy-action: Official IPFS GitHub Action for deploying static...](https://github.com/ipshipyard/ipfs-deploy-action)**
>
> Official IPFS GitHub Action for deploying static sites (or builds) to IPFS nodes/pinning services with CAR files, and addressing site builds with CIDs

### What makes this action different?

- Uses CAR files to ensure consistent CIDs across providers
- Primary deployment to Storacha/Kubo/IPFS Cluster with optional additional Pinata/Filebase pinning for redundancy
- Automatic preview links and PR/commit status updates
- Zero opinions about your build process - works with any static site

### Key Features

📦 Merkleizes your static site into a CAR file  
🚀 Multiple provider options: Storacha, IPFS Cluster, or Kubo  
📍 Optional Pinata pinning for redundancy  
💾 Optional CAR file upload to Filebase  
💬 Automatic PR comments with CID and preview links  
✅ Commit status updates

### Note on why it uses CAR files?

The action merkleizes your build into a CAR file right in GitHub Actions using ipfs-car. This ensures your CID is generated during the build process and remains consistent across providers - no more CID mismatches!

### Use it for publishing other data to IPFS?

While intended for static sites, you can also use the action for arbirary data, like build artefacs, that you may want to publish/pin to IPFS.

* * *

Check it out here: [Deploy to IPFS Action](https://github.com/ipfs/ipfs-deploy-action)

Built and maintained by [Interplanetary Shipyard](https://ipshipyard.com/).

Would love to hear your feedback (either here or in the GitHub repo), if you give it a try!

---

<div class="post-metadata">

**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\
**Post date:** [January 14, 2026, 3:54pm UTC](https://discuss.ipfs.tech/t/introducing-a-modern-github-action-for-deploying-sites-to-ipfs-built-for-2025/19007/2 "2026-01-14T15:54:23Z")

</div>

Now that Fleek is going down, this is becoming even more important. Unfortunately, due to the fact it uses the old “w3” CLI to deploy to Storacha, it fails miserably, as it is marked deprecated.

When can we expect this to be updated to the new “storacha” CLI?

---

<div class="post-metadata">

**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Post date:** [January 14, 2026, 4:24pm UTC](https://discuss.ipfs.tech/t/introducing-a-modern-github-action-for-deploying-sites-to-ipfs-built-for-2025/19007/3 "2026-01-14T16:24:26Z")

</div>

Thanks for raising this. There’s an open PR to get this resolved ( [fix: Update Storacha CLI package and commands by joshdougall · Pull Request #40 · ipshipyard/ipfs-deploy-action · GitHub](https://github.com/ipshipyard/ipfs-deploy-action/pull/40) ). I’ll ping @lidel to take a look a look.