* Use Python 3.11
* Run pyupgrade with Python 3.11+
* Update pyupgrade to latest version
* Update Celery and python-dateutil
Celery is not compatible with Python 3.11, leading to test failures. Need to update also python-dateutil to install the latest version.
* pytest.yield_fixture is a deprecated alias for pytest.fixture
* Update Django dev dependencies
* Update bleach
* Upgrade existing dependencies within the given constraints of the input files
* Fix jinja after update
* Update pip-tools
* Update django-* libraries
* Upgrade graphene-django
* Upgrade Django to 4.0
* Drop pytz
* ALLOWED_HOSTS must be a list
* Upgrade Django to 4.1
* Add workaround for the Raygun AttributeError
See:
https://github.com/MindscapeHQ/raygun4py/issues/108
* Avoid ValueError when instance doesn't have a primary key value but relationship is used.
See:
7ba6ebe914
* Upgrade Django to 4.2.11
* Drop pytz as a direct requirement
Fluent Rich editor has a special UI for messages with access keys, which lists access key candidates. We now use the same logic when
pretranslating accesskeys and save the first candidate as the pretranslation.
Also: Remove regex dependency and use the built-in re.
- Ignore resolver deprecation warning on make requirements
- Ignore egg fragment deprecation warning on make requirements
- Update test requirements (needed to update black)
- Update black (needed to install the regex package)
- Run make black
- Add regex package (needed to implement accesskey candidate generator)
* Update to compare-locales 9.0.1, fluent-syntax 0.19.0, pip-tools 6.13.0
The transitive dependency typing-extensions is also updated to 4.5.0
* ci: Use codecov action rather than the removed/deprecated pypi & npm packages
Usually, separating scheduler and execution worker is recommended, but we break that pattern intentionally in order to run the task exactly when scheduled.
Co-authored-by: Francesco Lodolo <flod@lodolo.net>
* Gracefully handle Google AutoML error when credentials not set
* Prevent app crash on Heroku by forcing protobuf to use Python for parsing
By default, protobuf uses C++ for parsing. The library includes prebuilt binary modules for Apple silicon, which my local box uses, so for me the
library works as expected without this hack. I only noticed that's not the case for everyone after deploying to the stage server on Heroku.
Read more:
https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updateshttps://developers.google.com/protocol-buffers/docs/reference/python-generated#sharing-messages
* Add buildpack needed for authentication using Google Cloud service accounts
And while we're at it, let's remove the unused buildpack.
- Adds a contact email field to user settings.
- Implements verification process: sends unique verification URL with a token to that email address.
Co-authored-by: Eemeli Aro <eemeli@gmail.com>
* refactor(tag-admin): Use functional components, stop testing internals
* style(tag-admin): Satisfy Prettier
* chore(tag-admin): Add & configure build with Rollup
* chore: Drop webpack dependencies as unused
terser is included in the root package.json to ensure its availability
for pipeline during the Django build via TERSER_BINARY.
* chore(tag-admin): Add npm install & build targets to Makefile
Also sets engine-strict = true in .npmrc, so attempts to use
npm cli versions which do not support workspaces will fail.
* chore(tag-admin): Update from rollup-plugin-replace to @rollup/plugin-replace
* docs: Update prerequisites
* Update lxml
* Update new frontend dependencies by running `yarn upgrade` in /frontend
* Update old frontend dependencies by regenerating package-lock.json using `npm i --package-lock-only`.
* Replace Array<React.ReactNode> with React.ReactNodeArray to match react-content-marker
* fix: EditorMainAction buttons were always ignoring warnings
Calling `sendTranslation(reactEvent)` resulted in considering
the first argument `ignoreWarnings` as true-ish.
* chore: Update compare-locales to 8.2.0
Using constraints has the benefit that updates to default.in only
show up in default.txt, and not in dev.txt. That should make reviews
easier. It still ensures there's only one version of each package
used across production, dev, and local testing.
* App configs are now automatically discovered, and most of our current app configs were redundant or had wrong names.
* The DEFAULT_AUTO_FIELD is needed to prevent unwanted migrations in the future, when the default value will change to BigAutoField.
* Make get_stats_sum return dict instead of AggregatedStats instance. Django 3.2 throws an error when instantiating an abstract model. Add tests for the relevant views that were previously not covered, marked with pytest.mark.no_cover.
Dj.debug brings some utils to help with development, but
we don't seem to be using it much, because it doesn't support Python 3
and we haven't noticed it so far.