- (dev dep only)
@iarna/toml
has a 3.0 that we have never been on but it was released the same day as the last 2.x https://github.com/BinaryMuse/toml-node/commits/master (needs more investigation)
- (Optional) Update minor dependencies in package.json
npx npm-check-updates
- or
npm outdated
+npm update --save
- If the minimum Node version changed, make sure you update
package.json
engines property.- Make sure the error message works correctly for Node versions less than 10.
- 0.12.x+ requires Node 10+
- 1.x+ requires Node 12+
- 2.x+ requires Node 14+
- 3.x+ requires Node 18+
- Make sure the error message works correctly for Node versions less than 10.
rm -rf node_modules && rm -f package-lock.json && npm install
npm audit
- Make sure
npm run check
(eslint) runs okay - Make sure
npm run test
(ava) runs okay - Update version in
package.json
- (Alpha) Use
-alpha.1
suffix - (Beta) Use
-beta.1
suffix
- (Alpha) Use
- Run
npm run coverage
- Check it all in and commit
- Tag new version
- Wait for GitHub Actions to complete to know that the build did not fail.
- Publish a release on GitHub at https://github.com/11ty/eleventy/releases pointing to the tag of the release. Hitting the publish button on this workflow will use GitHub Actions to publish the package to npm on the correct dist-tag and includes npm package provenance for the release.
- Main release: no version suffix publishes to
latest
(default) tag on npm- Make sure to include OpenCollective usernames for release notes here https://www.11ty.dev/supporters-for-release-notes/
- Canary release:
-alpha.
version suffix inpackage.json
publishes tocanary
tag on npm: #2758 - Beta release:
-beta.
version suffix publishes tobeta
tag on npm
Unfortunate note about npm and tags (specifically canary
here): if you push a 1.0.0-canary.x to canary
(even though 2.0.0-canary.x
exists), it will use the last pushed tag when you npm install from @canary
(not the highest version number)
- Maybe search for
-alpha.
(-canary.
?) or-beta.
in the docs copy to update to the stable release, if applicable. - Check in a new
11ty-website
site with updatedpackage.json
version. - Add version to
11ty-website
versions.json
- Commit it
- Create a new branch for branched version
- (Main) Check out the previous version git branch and add
outdated: true
to_data/config.json
and commit/push. - Go to https://app.netlify.com/sites/11ty/settings/domain and set up a subdomain for it.
- Update
eleventy-base-blog
to use new version - Update
11ty-website
to use new version