* include check-run in workflows where secrets are used
* revert changes in build-cli workflow and add check-run to codecov
* assert token permissions
* include required permissions
* re-arrange permissions in alphabetical order
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
* include check-run in workflows where secrets are used
* revert changes in build-cli workflow and add check-run to codecov
* assert token permissions
---------
Co-authored-by: Matt Bishop <mbishop@bitwarden.com>
Utilizing resources based on thread availability improves performance vs fixed threading.
The linked issue for CI crashes has not been closed. Once this is solves, `runInBand` may improves performance in CI.
* Update .nvmrc from v18 to v20
* Update engines setting node 18->20 and npm 9->10
* Use yao-pkg/pkg instead of vercel/pkg
---------
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Update build pipeline for beta labelling
* [PM-7663] Incorporate build workflow for the Chrome manifest v3 beta
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Update build pipeline for beta labeling
* [PM-7663] Ensure we can have a valid version number based on the github run id
* [PM-7663] Ensure we can have a valid version number based on the github run id
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting change made to the run id, as it will not function
* [PM-7663] Reverting a typo
* Fix Duplicate `process.env
* Learn how to use
---------
Co-authored-by: Justin Baur <19896123+justindbaur@users.noreply.github.com>
* Initial run to see what data I can access
* Update to use JQ
* Use dev action
* Implement artifact build sha
- Moved notify job to happen post artifact check
- Removed git sha job
- Updated jobs to use real artifact sha
* Update .github/workflows/deploy-web.yml
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* Handle web build triggers
- Update GH environment with commit as well
---------
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* [PM-7527] Get MV3 build artifacts in main branch with clear messaging that that the build is not to be released
* [PM-7527] Add `Build Manifest v3` build step to the build-browser.yml Github action
* [PM-7527] Get MV3 build artifacts in main branch with clear messaging that that the build is not to be released
* Update .github/workflows/build-browser.yml
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
---------
Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com>
* DEVOPS-1843 REFACTOR: Trigger web vault deploy step to send the build-web run-id to deploy-web workflow
* DEVOPS-1843 ADD: build-web-run-id input to deploy-web workflow to download specific run_id artifact
* DEVOPS-1843 FIX: build-web-run-id input in build-web workflow
* DEVOPS-1843 REFACTOR: build-web-run-id parameter type to number
* DEVOPS-1843 ADD: build-web-run-id input to deploy-web workflow to workflow_dispatch
* DEVOPS-1843 FIX: build-web-run-id type in deploy-web.yml
* DEVOPS-1843 REFACTOR: web vault deploy action to use GitHub Run ID
* DEVOPS-1843 REFACTOR: cloud asset download steps in deploy-web.yml
* DEVOPS-1843 REFACTOR: description for build-web workflow Run ID
Co-authored-by: MtnBurrit0 <77340197+mimartin12@users.noreply.github.com>
---------
Co-authored-by: MtnBurrit0 <77340197+mimartin12@users.noreply.github.com>
* Switch from timestamp to hash comparison
* Switch flag placement
* Add a value to the --compare-hash option
* Setting compare-hash to a string value
* undo debug default
