Piotr Galar

Yes, exactly! Pinning actions by hash is a mitigation for a potential supply chain attack. We try to do that for all actions that are neither from PL orgs nor...

We're moving the RC1 release to Monday (2022-09-26) to give enough headway for merging `What's left for release`. As of now, the rest of the schedule remains unchanged.

Early testers ping for RC1 testing 😄 - [ ] pacman.store (@RubenKelevra) - [ ] Infura (@MichaelMure) - [ ] Textile (@sanderpick) - [ ] Pinata (@obo20) - [ ]...

Agreed, it would be beneficial to have it ready in time for the RC. BTW, here's a draft changelog that @ajnavarro prepared - https://github.com/ipfs/kubo/blob/v0.16.0-rc1/docs/changelogs/v0.16.md. It's also linked from the release....

We have successfully release v0.16.0: https://github.com/ipfs/kubo/releases/tag/v0.16.0

Current status: I managed to successfully run all the workflows from CircleCI in GitHub Actions. Tracked in https://github.com/galargh/go-ipfs/tree/github-actions Next steps: set up self-hosted runners to boost performance. 30m+ builds are...

Rollout plan: - [x] Merge PR introducing new GitHub Actions workflows that are to replace the CircleCI ones ([PR](https://github.com/ipfs/kubo/pull/9355)) - [x] Verify the new wokflows running on GitHub-hosted machines are...

According to CircleCI's blog (https://support.circleci.com/hc/en-us/articles/360008097173-Troubleshooting-why-pull-requests-are-not-triggering-jobs-on-my-organization-) it can happen when: 1. ❎ you revoked OAuth access to CircleCI on your VCS provider (GitHub, BitBucket) 1. ❓ you're following the fork instead...

Thanks for checking! Btw, I also test opened two PRs, one from my priv account - https://github.com/ipfs/kubo/pull/9268 - and the other from my test org - https://github.com/ipfs/kubo/pull/9269 - and they...

Quick update: we're not addressing this issue in the hope we can deliver https://github.com/ipfs/kubo/issues/8804 instead which would mean we're completely off of CircleCI.