* Align dist and release tags on all platforms
* Upload web sourcemaps
* Debug code
* Send debug and error logging to Sentry
* Let .env do the work
* Try straight env
* Try copy in Dockerfile
* Ok ok ok
* Debug Dockerfile
* Proper setup
* See where we're at
* Reference var correctly
* Fall back to package version
* Verbose force env
* Should be working native builds
* Comments
* Remove unused deps
* Revert unneeded changes
* Remove debug code
* Clarify intent
* Remove deprecated files
* Add sentry vars to OTA
* Debug
* Revert "Debug"
This reverts commit 2d5857fb0fb0858ac3e2f98bc56bde913078d0a7.
* Use included CLI to upload native source maps post-OTA build
* Use included bin script
See https://github.com/getsentry/sentry-react-native/commit/0d87adb516b2a5ea61353e25098c31f9aeb7e503
* Bump sentry, update script
* Comment
* fix failing CI
* Pin sentry, update patch, update lock
---------
Co-authored-by: Samuel Newman <mozzius@protonmail.com>
* Update Node.js to 20.x in Dockerfile
* Update Node.js types and engines entry to 20.x
* Update Node.js version in .nvmrc
* Use node version from .nvmrc in linting job
* Use Type Assertion for clearTimeout
* use env variables through docker args
* remove quotes
* use an output instead
* try that again
* write the variables to .env
* rm unused
* use short sha
* remove test branch
* Install lingui eslint plugin, ignore compiled files
* Add lingui step to Lint workflow
* Run check in other job
* Add compile step to web build
* Temp: add a new string to test with
* Add message
* Revert "Temp: add a new string to test with"
This reverts commit ef5459d00c.
* Un-track compiled files
* Add check scripts to package.json, build step
* Make sure to compile translations prior to test/typecheck
* Rename scripts
* top-level Makefile
The primary motivation here is the `build-web` command, which calls the
yarn build and then also copies over JS files. The Dockerfile does this
and I always forget when doing it manually.
* build-web: cp bundles in yarn command, not Makefile+Dockerfile