This repository was archived by the owner on Feb 12, 2024. It is now read-only.
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
⚡️ v0.42.0 RELEASE 🚀 #2808
Closed
Description
Bug fixes
🗺 What's left for release
- fix: CLI mkdir/touch/write does not support --mtime-nsecs CLI mkdir/touch/write does not support --mtime-nsecs #2803
- fix: Remove ky Tracking issue for
kyremoval #2801 - fix: webui in jsipfs didn't auto set port to 5002 webui in jsipfs didn't auto set port to 5002 #2781
- fix: IPFS Fails to start with nodejs_gc_runs_total has already been registered IPFS Fails to start with nodejs_gc_runs_total has already been registered #2019
🚢 Estimated shipping date
27th March
🔦 Highlights
- Bug fixes
🏗 API Changes
ipfs.files.statwould returnhamt-sharded-directorywhen statting a HAMT Shard, it now returnsdirectoryin line with go-IPFS.
✅ Release Checklist
- Stage 0 - Automated Testing
- Feature freeze. If any "non-trivial" changes (see the footnotes of docs/releases.md for a definition) get added to the release, uncheck all the checkboxes and return to this stage.
- Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes:
- unit/functional/integration/e2e
- interop
- all the examples run without problems
- IPFS application testing
- Third party application testing
- Stage 1 - Internal Testing
- Documentation
- Ensure that README.md is up to date
- Install section
- API calls
- Packages Listing
- Ensure that README.md is up to date
- Network Testing:
- test lab things - TBD
- Infrastructure Testing:
- TBD
- Documentation
- Stage 2 - Community Dev Testing
- Reach out to the IPFS early testers listed in docs/EARLY_TESTERS.md for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR.
- Reach out on IRC for additional early testers.
- Stage 3 - Community Prod Testing
- Update js.ipfs.io examples to use the latest js-ipfs
- Invite the IPFS early testers to deploy the release to part of their production infrastructure.
- Invite the wider community (link to the release issue):
- discuss.ipfs.io
- IRC
- Stage 4 - Release
- Take a snapshot of everyone that has contributed to this release (including its direct dependencies in IPFS, libp2p, IPLD and multiformats) using the js-ipfs-contributors module.
- Publish to npm:
# In the root of the repo, run the following commands and follow the on-screen prompts: npm run reset && npm i npm run release
- Publish a blog post to github.com/ipfs/blog (at minimum, a c&p of this release issue with all the highlights, API changes and thank yous)
- Broadcasting (link to blog post)
- IRC
- discuss.ipfs.io
- Announce it on the IPFS Users Mailing List
- Copy release notes to the GitHub Release description
❤️ Huge thank you to everyone that made this release possible
- @achingbrain (149 commits, 44 PRs, 6 issues, 166 comments)
- @agustinmessina (3 comments)
- @alanshaw (8 commits, 6 PRs, 1 issue, 12 comments)
- @alexjc (1 issue, 1 comment)
- @andrew (7 commits, 14 PRs, 1 comment)
- @aphelionz (1 PR, 1 issue, 3 comments)
- @aquiladev (1 issue)
- @betamos (1 issue)
- @bluelovers (2 commits, 8 PRs, 14 issues, 26 comments)
- @calikevuche (2 issues, 1 comment)
- @carsonfarmer (3 comments)
- @chafey (2 commits, 4 PRs, 4 issues, 9 comments)
- @ChainSafeSystems (1 comment)
- @christopheSeeka (2 issues, 7 comments)
- @CLAassistant (1 comment)
- @codecov-io (4 comments)
- @daviddias (2 commits, 3 PRs, 1 issue, 7 comments)
- @dirkmc (1 PR, 5 comments)
- @Elvenisboy (1 comment)
- @emclab (3 comments)
- @Gudahtt (1 issue)
- @hacdias (2 commits)
- @happy-zhangbo (2 issues, 2 comments)
- @hazae41 (2 issues)
- @hsanjuan (3 comments)
- @hugomrdias (39 commits, 27 PRs, 6 issues, 35 comments)
- @icidasset (2 issues, 3 comments)
- @iRyanBell (1 PR)
- @jacobheun (45 commits, 3 PRs, 3 issues, 36 comments)
- @Jonybang (1 issue)
- @josselinchevalay (1 issue, 4 comments)
- @jsonsivar (2 issues)
- @kalmi (1 issue, 1 comment)
- @kanej (1 commit, 1 PR, 2 comments)
- @kawmaiparis (1 issue, 1 comment)
- @koivunej (1 issue)
- @kumavis (1 commit, 1 PR, 2 comments)
- @latenssi (1 issue, 2 comments)
- @lidel (1 PR, 2 issues, 4 comments)
- @MaduraRaj (1 issue)
- @MaxGraey (1 comment)
- @mcclure (1 issue)
- @mell-old (1 issue)
- @mfsoftworks (1 comment)
- @mikeal (1 issue, 12 comments)
- @mkg20001 (4 commits, 1 issue, 4 comments)
- @mmm8955405 (1 issue, 6 comments)
- @MonarthS (1 comment)
- @mpetrunic (1 PR)
- @nijynot (1 commit)
- @notsag-dev (1 PR)
- @npfoss (1 commit)
- @obo20 (1 issue, 3 comments)
- @olizilla (1 commit, 1 PR, 2 comments)
- @ottodevs (5 comments)
- @pcowgill (2 PRs, 8 issues, 43 comments)
- @ribasushi (1 issue, 1 comment)
- @rigwild (1 comment)
- @robertkiel (6 commits, 6 PRs, 1 comment)
- @rvagg (1 PR, 7 comments)
- @SahidMiller (1 comment)
- @sbhamad (1 issue)
- @Schwartz10 (1 comment)
- @sebastiendan (2 issues, 9 comments)
- @SignpostMarv (2 issues, 2 comments)
- @siman (2 comments)
- @sinkuu (1 comment)
- @stale (1 comment)
- @Stebalien (2 commits, 2 PRs, 1 issue, 9 comments)
- @svdo (1 PR, 1 comment)
- @tabcat (2 commits, 2 PRs, 1 issue)
- @tniessen (1 issue)
- @tuyennhv (1 PR, 1 comment)
- @uchetron (1 issue)
- @ulvus (1 comment)
- @vasco-santos (72 commits, 17 PRs, 17 issues, 78 comments)
- @vaultec81 (2 issues, 10 comments)
- @vmx (12 commits, 9 PRs, 11 comments)
- @warpfork (1 comment)
- @wemeetagain (1 commit, 1 comment)
- @whyrusleeping (1 comment)
- @wolfgang (1 comment)
- @woss (1 comment)
- @x5engine (1 comment)
- @Xmader (1 commit, 1 PR)
- @xmaysonnave (1 issue, 1 comment)
- @zebateira (1 PR)
- @zot (1 comment)
🙌🏽 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:
- Check the issues with the
help wantedlabel in the js-ipfs repo - Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
- Join the discussion at https://discuss.ipfs.io/ and help users finding their answers.
- Join the 🚀 IPFS Core Implementations Weekly Sync 🛰 and be part of the action!
⁉️ Do you have questions?
The 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.
Metadata
Metadata
Assignees
Labels
No labels