* 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
* Drop pontoon/in-context/
* Drop subpages
* Drop project links, url & width fields
* Drop pontoon.js
* Drop remaining mentions of in-context localization
* 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.
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
Replace django-pylibmc with django-bmemcached, which is recommended by
other Heroku users. We also update app.js (used during Deploy with
Heroku button) and docs to use Memcachier add-on instead of Memcached
Cloud.
* Update version of buildpack for git submodules
* Add SITE_URL setting to app.json and mark as required
* Remove code responsible for automatic discovery of SITE_URL after a
deploy on Heroku
* Add runtime.txt and set python2 as the default for python buildpack
Matjaž Horvat
Eemeli Aro
Eemeli Aro
Woosuk Park
Jarek
Adrian Gaudebert
Jarek
Jarek