Jira Assistant final Release testing and Publish process
Once your development work is complete and the latest code is available in the "develop" branch, it needs to be merged into the "package" branch. The package to be published will be built from the "package" branch. Before merging, make sure to update the version number in all
manifest.json files under the "public" folder.
To build the package, follow these steps:
node_modules folder, as it can sometimes cause issues during the webstore review process.
npm install --force and wait for the process to complete.
npm run build. This will generate packages for various browsers under the "build" folder.
Steps to Download GitHub Automated Build Package:
Currently, only Shridhar (the developer) has the privilege to publish the package to the web store. Automation of this step may be considered in the future, or additional contributors may be granted this privilege.
The build package generated from the above steps can be temporarily loaded for testing purposes. Use the appropriate version for each browser, such as Chrome, Firefox, Edge, and Opera.
Steps for Loading the Temporary Extension:
chrome folder from the build output directory.
firefox folder from the build output directory.
edge folder from the build output directory.
opera folder from the build output directory.
Please note that some browsers, like Firefox, will automatically remove temporarily loaded add-ons when the browser is closed. Therefore, this option is only suitable for testing and not a permanent solution.