-
Notifications
You must be signed in to change notification settings - Fork 9
Releases
Juliette Regimbal edited this page Feb 19, 2020
·
2 revisions
This is a reminder on what to do when making a new release of Neon. This should always be done off of the master branch.
- Include a changelog in the release notes.
- Have the release number present in
README.md
,webpack.config.js
,webpack.pages-config.js
, andpackage.json
. - Ensure the CI status badge displayed on the readme is pointing at the master branch, not the develop branch.
- Regenerate typedocs and clear old ones first so there are not extra files.
After the release, do the following:
- Update the version hosted on GitHub pages.
- Update the master version of Neon used on neon-wrapper.
© 2018-2020 Distributed Digital Archives and Libraries Lab