Skip to content
Michael Schaller edited this page Dec 10, 2023 · 9 revisions

Resume YouTube Subs extension wiki

For general details on the extension see README.md.

Release instructions

Step by step instructions how to release the Resume YouTube Subs Chrome extension.

  1. Install the git and jq tools. This only needs to be done once.
    Under Ubuntu/Debian/Mint Linux you can install them by running:

    sudo apt install git jq
  2. Change the working directory of your shell to the main directory of the extension code (the directory with manifest.json).

    Note: All commands are intended for the Bash shell under Linux.

  3. Double check files for remaining TODOs that should be resolved as part of this release.

    grep -rInH --exclude-dir=.git TODO .
  4. Test the extension multiple times (at least 10 times each) for each supported configuration.
    The supported configurations are:

    1. Chrome stable + The YouTube subscriptions page in grid view.
    2. Chrome stable + The YouTube subscriptions page in list view.
  5. Make sure the documentation is up to date. Double check the following files:

    1. README.md
    2. Wiki
  6. Increase the extension version in manifest.json. The version number adheres to the semantic versioning rules.

  7. Commit the changes after double checking that all new files (if there are any) are actually included in the commit(s).

  8. Tag HEAD commit with the new version from manifest.json.

    version=$(jq -r '.version' manifest.json) && git tag "v${version}" HEAD
  9. Push commit(s) and new version tag upstream.

    git push origin --tags
  10. Create a zip archive of the extension for the upload to the Chrome Web Store.

    Note: The zip archive will be created in the parent directory.

    version=$(jq -r '.version' manifest.json) && git archive -o "../resume-youtube-subs-${version}.zip" -9 "v${version}"
  11. Upload the zip archive to the Chrome Web Store Developer Dashboard via the New item button.

  12. Once the update of the extension is approved double check that the update actually is published.

Clone this wiki locally