Make sure the CI is running: https://github.com/configcat/js-chromium-extension-sdk/actions/workflows/js-chromium-ci.yml
-
Run
./deploy.sh
-
Make sure new package is available via NPM: https://www.npmjs.com/package/configcat-js-chromium-extension
-
Add release notes: https://github.com/configcat/js-chromium-extension-sdk/releases
-
Update
configcat-js-chromium-extension
dependency in all sample applications, and test them by following theirREADME.md
.
or
-
Run tests
npm test
-
Create a new version (patch, minor, major) Increase version number by using
npm version patch | minor | major
Example: increasing patch version
npm version patch
-
Push tag to remote
If you tag the commit, a GitHub action automatically publishes the package to NPM.
git push origin <new version>
Example: git push origin v1.1.17
You can follow the build status here -> https://github.com/configcat/js-chromium-extension-sdk/actions/workflows/js-chromium-ci.yml
-
Make sure new package is available via NPM: https://www.npmjs.com/package/configcat-js-chromium-extension
-
Add release notes: https://github.com/configcat/js-chromium-extension-sdk/releases
-
Update
configcat-js-chromium-extension
dependency in all sample applications, and test them by following theirREADME.md
.