forked from mozilla/pontoon
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update instance to the latest #1
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.21. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.15...4.17.21) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Also: reflect django-dotenv update in the rest of the requirements files
Also remove media/ subfolders.
* Prepare for typescript in core/api/base * Prepare for typescript in core/lightbox * Prepare for typescript in core/loaders * Prepare for typescript in core/plural * Prepare for typescript in core/entities
Bumps [jinja2](https://github.com/pallets/jinja) from 2.10.1 to 2.11.3. - [Release notes](https://github.com/pallets/jinja/releases) - [Changelog](https://github.com/pallets/jinja/blob/master/CHANGES.rst) - [Commits](pallets/jinja@2.10.1...2.11.3) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [pygments](https://github.com/pygments/pygments) from 2.1 to 2.7.4. - [Release notes](https://github.com/pygments/pygments/releases) - [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES) - [Commits](pygments/pygments@2.1...2.7.4) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Which suppresses warnings when the dotenv file is missing among other things.
* 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.
The previous version was incompatible with Django 3.2.
Also: Use --pretty to get error stats in flow-to-ts.
Log the following actions: * Render: Unread notifications icon * Click: Notifications icon * Background action: Mark all notifications as read * Page load: Notifications Also: * Make CSRF token globally accessible on the base template * Always mark notifications as read when notification menu opens * Unify animation time between translate page and other pages
Show Pontoon Add-On promotion on each page, unless: - Add-on installed - Promotion dismissed - User not authenticated - Non-supported browser used (Add-On only supports Firefox and Chrome) Also use the base template properly in the Machinery template.
This makes use of the new admin.display decorator from Django 3.2. Additionally, we use format_html instead of mark_safe.
Synthetic events are only if you use the handler as jsx prop, but when you do addEventHandler (and remove), you want to use native event types. This is another cleanup for TS, but also fixes some flow-ignores. * Use MouseEvent for onDiscard * Use MessageEvent for addonpromotion * Use KeyboardEvent for search shortcuts * Use Event for scroll events in comments * Use KeyboardEvent for batch shortcuts * Use KeyboardEvent for entitieslist shortcuts * Use KeyboardEvent for entity navigation shortcuts * Use unspecific synthetic event for onSubmit
* Update pip-tools to v6.6.1 (fixes when using pip 22.1) * set tomli to v1.2.2 * Full 'make requriements' output
Limits the parser and serializer exports to parseEntry() and serializeEntry functions, rather that the previously exposed entire object instances.
…)" (mozilla#2533) This reverts commit 83d723f.
Refactor editor state management
* Refactor PluralForm context & useSelectedEntity() into EntityView context * Drop unused/unnecessary/obsolete code from batchactions & history * Refactor redux HistoryState into HistoryData context * Refactor redux NotificationState into NotificationMessage & ShowNotification contexts * Move providers from EntityDetails to Entity, dropping their props
Co-Authored-By: Manish Goregaokar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current instance has an issue around authentication, see https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/www.2Erust-lang.2Eorg.20Pontoon.20translations.
This pulls the latest code from upstream to update deps/code and try to fix that issue. I haven't tested well, just checked the server started fine, so it'd be great if we could do a staging deployment before landing on a production to see if the current translation work doesn't go away.