Refactor the remaining logic from gulp. Part of the browser build script
refactor effort.
Webpack is now responsible for performing most of the operations previously
done by gulp. This includes: - Setting browser specific class - Building the
manifest file The `package.json` is modified to include browser specific
commands for `build`, `build:prod`, `build:watch` and `dist`.
# Manifests
Manifests now uses the `copy-webpack-plugin` `transform` feature. The logic is
located in `apps/browser/webpack/manifest.js`. It reads a template, which
supports some basic operations primarily overriding with browser specific
fields using `__browser__`. The `manifest.json` for both regular and mv3
builds are identical to our existing manifests except:
- `applications` renamed to `browser_specific_settings`.
- `permissions` sorted alphabetically.
# Safari build
Safari requires additional packaging commands. This is implemented as a
powershell script due to the cross-platform nature, and since we generally
require powershell in our distribution pipelines. An alternative would be to
write it in bash, but bash is less powerful and would require some additional
commands like `jq`. Another alternative is to write it using js, but that would
require additional dependencies.
Refactor the remaining logic from gulp. Part of the browser build script
refactor effort.
Webpack is now responsible for performing most of the operations previously
done by gulp. This includes: - Setting browser specific class - Building the
manifest file The `package.json` is modified to include browser specific
commands for `build`, `build:prod`, `build:watch` and `dist`.
# Manifests
Manifests now uses the `copy-webpack-plugin` `transform` feature. The logic is
located in `apps/browser/webpack/manifest.js`. It reads a template, which
supports some basic operations primarily overriding with browser specific
fields using `__browser__`. The `manifest.json` for both regular and mv3
builds are identical to our existing manifests except:
- `applications` renamed to `browser_specific_settings`.
- `permissions` sorted alphabetically.
# Safari build
Safari requires additional packaging commands. This is implemented as a
powershell script due to the cross-platform nature, and since we generally
require powershell in our distribution pipelines. An alternative would be to
write it in bash, but bash is less powerful and would require some additional
commands like `jq`. Another alternative is to write it using js, but that would
require additional dependencies.
* Updated release jobs to include fixes that Vince recommended from the mobile repo
* Updated the workflows with the fixes
that Vince recommended from mobile.
* Fix linter errors
Co-authored-by: Todd Martin <>
Co-authored-by: Michal Checinski <michal.checinski@outlook.com>
* [ENG-71] updated release-web.yml to add deployment updates.
* [ENG-71] Added newline at the end of the file
* [ENG-71] Changed environment name.
* [ENG-71] Changed branch name again.
* Fixed error in brackets.
* Added release version
* [ENG-71] Updated all the other scripts to track deployments.
* [ENG-71] added channel
* [ENG-71] Added newline
* [ENG-71] Removed separate deployments for choco and snap
* [ENG-71] Removed separate deployments
* [ENG-71] Added newline
* [ENG-71] refined messages
* [ENG-71] Changed to separate out environment and description.
* [ENG-71] more changes to sepearate environment from description
* Job cleanup
* Job cleanup
* [ENG-71] More job cleanup
* [ENG-71] Updated to use commit instead of v2.
* [ENG-7] Fixed error referencing release-version
Co-authored-by: Todd Martin <>
* disabling snap for testing
* adding in environment logging
* adding in some Dry Run logic
* adding more protected dry run logic
* skipping long running steps for testing purposes
* testing out windowws-2022 runner
* Trying a different GitHub Action expression syntax
* manually disabling jobs because I don't have time to figure out GitHub's weird syntax
* updating nuget on windows-2019
* disabling the nuget version 6
* trying more GitHub Action syntax
* disabling choco for testing
* running test on Dry Run release
* changing the double quotes to single quotes inside the GitHub Action expression
* removing testing code
* updating more dry run logic
* reverting a branch name change
