When creating a Github release, such as stg-v3.1.1, we should update all **/package.json version fields to be the same version of that of the Github Release.
Check List
[x] add a script to @dzcode.io/tooling that takes a version as an argument and applies it across the repo's pakcage.json files
[x] modify the deploy workflows to run this script passing the {{ github.ref_name }} as argument.
[x] address #414
[x] do the same as point (3) but for ./mobile
[x] specify Sentry release for all apps, take it from package.json.version
Additional Comments
This will be helpful, for tracking progress, error logs, and overall making the monorepo's version consistent
Description
When creating a Github release, such as stg-v3.1.1, we should update all
**/package.json
version fields to be the same version of that of the Github Release.Check List
@dzcode.io/tooling
that takes a version as an argument and applies it across the repo'spakcage.json
files{{ github.ref_name }}
as argument../mobile
package.json
.version
Additional Comments
This will be helpful, for tracking progress, error logs, and overall making the monorepo's version consistent