-
Notifications
You must be signed in to change notification settings - Fork 1.2k
⚡️ v0.38.0 RELEASE 🚀 #2396
Comments
🚢 There's a pre-release version available for testing with the GC work in it |
🐣 |
🐤 0.38.0-rc.0 has been published! |
@achingbrain can you include #2428 so that it unblocks all the work on improved testing #2276? |
I'd rather not because the build for that PR is failing, |
In all honesty stages 2 & 3 are likely to be very short as the early testers list is pretty short so we can always start the |
🐥 0.38.0-rc.1 has been published! |
Also, the release is being done from a branch - |
A little late, but: 🐔 0.38.0-rc.2 has been published! (running out of chicken emojis, sorry) |
🍟 0.38.0-rc.5 has been published! This is planned to be the last rc before release and contains up to date documentation. |
@achingbrain does the number of unchecked boxes represent reality? |
More or less? It's up to date now. I left the stage headline checkbox unchecked if there were any steps missing so we have an easy view on what to improve next time. |
🗺 What's left for release
ipfs add
output fixes[ ] feat: Config profiles(moved to v0.39.0)ipfs resolve
Future release:
feat: Enable DHT in client modefeat: Reproviderfeat: Repo migration toolfix: Locking for concurrent pin opsfix: Offline blockstore for pinningperf: Cache to improve pin performancefix: Limit concurrent HTTP requests in browser🚢 Estimated shipping date
30th September
🔦 Highlights
🏗 API Changes
✅ Release Checklist
❤️ Huge thank you to everyone that made this release possible
🙌🏽 Want to contribute?
Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:
help wanted
label in the js-ipfs repoThe best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the
#ipfs
channel on Freenode.The text was updated successfully, but these errors were encountered: