You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
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
sharness (Does not run js-ipfs)
all the examples run without problems
IPFS application testing
webui (Does not depend on js-ifps or js-ipfs-http-client) #2542
ipfs-desktop (Does not depend on js-ifps or js-ipfs-http-client) #2542
# All succesful builds of master update the `build/last-successful branch which contains a npm-shrinkwrap.json.# This command checks that branch out, installs it's dependencies using `npm ci`, creates a release branch# (e.g. release/v0.39.x), updates the minor prerelease version (e.g. 0.38.0 -> 0.39.0-rc.0) and publishes it to npm
npx aegir publish-rc
# Later we may wish to update the rc. First cherry-picked/otherwise merged the new commits into the release # branch on github (e.g. not locally) and wait for CI to pass. First update the lockfiles used by ci (n.b. one # day this will be done by our ci tools):
npx aegir update-release-branch-lockfiles release/v0.39.x
# Then update the rc publisehd on npm. This command pulls the specified release branch, installs it's dependencies# `npm ci`, increments the prerelease version (e.g. 0.39.0-rc.0 -> 0.39.0-rc.1) and publishes it to npm
npx aegir update-rc release/v0.39.x
Network Testing:
test lab things - TBD
Infrastructure Testing:
TBD
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):
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:
git checkout release/v0.39.x
# Re-install dependencies using lockfile (will automatically remove your node_modules folder)# (Ensures the versions used for the browser build are the same that have been verified by CI)
npm ci
# lint, build, test, tag, publish
npm run release-minor
# reintegrate release branch into master
git rm npm-shrinkwrap.json yarn.lock
git commit -m 'chore: removed lock files'
git checkout master
git merge release/v0.39.x
git push
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.
The text was updated successfully, but these errors were encountered:
🗺 What's left for release
block rm
over HTTP APIFuture release:
feat: Enable DHT in client modefeat: Reproviderfeat: Repo migration toolfix: Locking for concurrent pin opsfix: Offline blockstore for pinningperf: Cache to improve pin performance🚢 Estimated shipping date
23rd October
🔦 Highlights
🏗 API Changes
✅ Release Checklist
sharness(Does not runjs-ipfs
)webui(Does not depend onjs-ifps
orjs-ipfs-http-client
) #2542ipfs-desktop(Does not depend onjs-ifps
orjs-ipfs-http-client
) #2542❤️ 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: