-
-
Notifications
You must be signed in to change notification settings - Fork 641
Releasing Dexie
TL;DR
Only for lead contributors with access to publish on npm.
- Have a dedicated master clone on your hard drive, for example
/c/repos/dexie-release
- Have nescessary npm packages installed globally (if any?... FIXTHIS)
Before releasing
- CD to your development clone of the develop branch and update from master.
git checkout develop
git merge master develop
-
Run unit tests in IE (or Edge), chrome (or opera) and firefox. TODO: Automate this throw browserstack.
-
Run the unit test addons/Dexie.Observable/test/test-observable-dexie-tests.html in chrome at least. One test fails and explains why. TODO: Make the test succeed and make sure to automate this as well.
-
CD to your dedicated 'dexie-release' location.
git checkout master
git pull
git status # should be clean
tools/release.sh
# enter new version number. If prerelase, use a pre-release version
# such as "1.3.5-beta"
Tests will run via karma. Script will publish on npm and checkin dist builded files into github/releases branch. 5. Browse to https://github.com/dfahlander/Dexie.js/releases and edit the new tag so that it becomes a release. Write release notes based on the commit history.
git reset --hard origin/master
Then, fix problems and re-run tools/release.sh
Dexie.js - minimalistic and bullet proof indexedDB library