This could fix the obscure "#ERROR# HttpError: Validation Failed" that
we're getting in failed actions.
Signed-off-by: Ekaterina Gerasimova <ekaterinag@element.io>
* Revert "Revert "Update minification and sourcemap settings on CI builds for sentry (#19583)" (#19601)"
This reverts commit 516e38c82d.
* Disable minification in CI as it exceeds memory limits for poor buildkite
With previous settings, our JS files for develop are so large that sentry's webserver rejects the upload.
* re-enable minification to reduce the size of the files
* update the CI sourcemap setting from eval-source-map to source-map to move the embedded source out of the .js payload and into .js.map files
Merge issues-to-projects and triage-needs-info into one under a new name
as they have the same trigger.
Add automation to move ex-needs info issues to triaged when labels are
updated.
Fixes#18523
Signed-off-by: Ekaterina Gerasimova <ekaterinag@element.io>
All incoming issues labelled with A-E2EE* and A-*spaces* labels should go to appropriate teams, and not to P1 in the web app team project.
Signed-off-by: Ekaterina Gerasimova <ekaterinag@element.io>
Fixes https://github.com/vector-im/element-web/issues/19485
The variable should be set when it needs to by CI, but in every other environment it's not important. Simply setting it to *something* makes EnvironmentPlugin happy. We print a warning just in case people expect it to be set, and use a clear value in case the environment variable doesn't get properly set.
This was completely unnecessary: react-sdk includes appropriate CSS
for highlight.js in its themes. This was actually causing some of
those values to be overridden with silly ones that made text invisible
on the dark theme.
Fixes https://github.com/vector-im/element-web/issues/19476
This was completely unnecessary: react-sdk includes appropriate CSS
for highlight.js in its themes. This was actually causing some of
those values to be overridden with silly ones that made text invisible
on the dark theme.
Fixes https://github.com/vector-im/element-web/issues/19476
* Deprecate `sso_immediate_redirect` and add welcome-page only option
The old `sso_immediate_redirect` option is kept in code for backwards compatibility, but is replaced by `sso_redirect_options.immediate`, where a new `on_welcome_page` option is also introduced to only target entry points to the app.
The path matching is a bit brittle, but still ideal in the sense of not showing UI while the app realizes it needs to redirect.
The new welcome page-only option is fully intended to avoid breaking permalinks and such while still redirecting when needed. In future, other options might be added here to further tune the experience.
* Add note about guests
