Add Filebase to the PSA compliance checker

[acejam]

Hi there,

We would like to add Filebase to the IPFS PSA compliance checker. The following SECRETS can be used:

• FILEBASE_API_ENDPOINT: https://api.filebase.io/v1/ipfs
• FILEBASE_API_TOKEN: Sign up for a free account at https://filebase.com and follow https://docs.filebase.com/storage-networks/ipfs/ipfs-pinning#re-pinning-existing-ipfs-cids-with-filebase-using-the-ipfs-cli to generate a token. We are also happy to provide a token out of band as well if needed.

[SgtPooki]

Secrets added. You should have permissions now @hacdias

[hacdias]

@acejam can you please rebase / merge with main to get all upstream fixes and updates?

[acejam]

@hacdias Done

[hacdias]

@SgtPooki I'm almost sure the failing tests are because the PRs don't have access to the secrets, right? How do we go in situations like this?

[SgtPooki]

I kicked off the action manually for a new branch I created from this PR filebase-addition: https://github.com/ipfs-shipyard/pinning-service-compliance/actions/runs/2950538940

---

edit: it succeeded. merging

[github-actions[bot]]

:tada: This PR is included in version 1.2.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[acejam]

@SgtPooki Thanks for merging! It looks like https://github.com/ipfs-shipyard/pinning-service-compliance/tree/gh-pages is still missing Filebase reports. Did I miss something in this PR?

[SgtPooki]

@acejam It's showing properly at https://ipfs-shipyard.github.io/pinning-service-compliance/api.filebase.io.html

[acejam]

@SgtPooki Yes, it is now, thanks to ff39295f0a08494758f81a82065e9e232a727284 👍