Add files using upload-large-folder tool

testbed/django__django/docs/releases/1.8.17.txt

@@ -0,0 +1,14 @@
+===========================
+Django 1.8.17 release notes
+===========================
+
+*December 1, 2016*
+
+Django 1.8.17 fixes a regression in 1.8.16.
+
+Bugfixes
+========
+
+* Quoted the Oracle test user's password in queries to fix the "ORA-00922:
+  missing or invalid option" error when the password starts with a number or
+  special character (:ticket:`27420`).

testbed/django__django/docs/releases/1.8.9.txt

@@ -0,0 +1,39 @@
+==========================
+Django 1.8.9 release notes
+==========================
+
+*February 1, 2016*
+
+Django 1.8.9 fixes several bugs in 1.8.8.
+
+Bugfixes
+========
+
+* Fixed a regression that caused the "user-tools" items to display on the
+  admin's logout page (:ticket:`26035`).
+
+* Fixed a crash in the translations system when the current language has no
+  translations (:ticket:`26046`).
+
+* Fixed a regression that caused the incorrect day to be selected when opening
+  the admin calendar widget for timezones from GMT+0100 to GMT+1200
+  (:ticket:`24980`).
+
+* Fixed a regression in 1.8.8 causing incorrect index handling in migrations on
+  PostgreSQL when adding ``db_index=True`` or ``unique=True`` to a
+  ``CharField`` or ``TextField`` that already had the other specified, or when
+  removing one of them from a field that had both, or when adding
+  ``unique=True`` to a field already listed in ``unique_together``
+  (:ticket:`26034`).
+
+* Fixed a crash when using an ``__in`` lookup inside a ``Case`` expression
+  (:ticket:`26071`).
+
+* Fixed a crash when using a reverse ``OneToOneField`` in
+  ``ModelAdmin.readonly_fields`` (:ticket:`26060`).
+
+* Fixed a regression in Django 1.8.5 that broke copying a ``SimpleLazyObject``
+  with ``copy.copy()`` (:ticket:`26122`).
+
+* Fixed the ``contrib.gis`` map widgets when using
+  ``USE_THOUSAND_SEPARATOR=True`` (:ticket:`20415`).

testbed/django__django/docs/releases/1.9.13.txt

@@ -0,0 +1,37 @@
+===========================
+Django 1.9.13 release notes
+===========================
+
+*April 4, 2017*
+
+Django 1.9.13 fixes two security issues and a bug in 1.9.12. This is the final
+release of the 1.9.x series.
+
+CVE-2017-7233: Open redirect and possible XSS attack via user-supplied numeric redirect URLs
+============================================================================================
+
+Django relies on user input in some cases  (e.g.
+``django.contrib.auth.views.login()`` and :doc:`i18n </topics/i18n/index>`)
+to redirect the user to an "on success" URL. The security check for these
+redirects (namely ``django.utils.http.is_safe_url()``) considered some numeric
+URLs (e.g. ``http:999999999``) "safe" when they shouldn't be.
+
+Also, if a developer relies on ``is_safe_url()`` to provide safe redirect
+targets and puts such a URL into a link, they could suffer from an XSS attack.
+
+CVE-2017-7234: Open redirect vulnerability in ``django.views.static.serve()``
+=============================================================================
+
+A maliciously crafted URL to a Django site using the
+:func:`~django.views.static.serve` view could redirect to any other domain. The
+view no longer does any redirects as they don't provide any known, useful
+functionality.
+
+Note, however, that this view has always carried a warning that it is not
+hardened for production use and should be used only as a development aid.
+
+Bugfixes
+========
+
+* Fixed a regression in the ``timesince`` and ``timeuntil`` filters that caused
+  incorrect results for dates in a leap year (:ticket:`27637`).

testbed/django__django/docs/releases/1.9.3.txt

@@ -0,0 +1,107 @@
+==========================
+Django 1.9.3 release notes
+==========================
+
+*March 1, 2016*
+
+Django 1.9.3 fixes two security issues and several bugs in 1.9.2.
+
+CVE-2016-2512: Malicious redirect and possible XSS attack via user-supplied redirect URLs containing basic auth
+===============================================================================================================
+
+Django relies on user input in some cases (e.g.
+``django.contrib.auth.views.login()`` and :doc:`i18n </topics/i18n/index>`)
+to redirect the user to an "on success" URL. The security check for these
+redirects (namely ``django.utils.http.is_safe_url()``) considered some URLs
+with basic authentication credentials "safe" when they shouldn't be.
+
+For example, a URL like ``http://mysite.example.com\@attacker.com`` would be
+considered safe if the request's host is ``http://mysite.example.com``, but
+redirecting to this URL sends the user to ``attacker.com``.
+
+Also, if a developer relies on ``is_safe_url()`` to provide safe redirect
+targets and puts such a URL into a link, they could suffer from an XSS attack.
+
+CVE-2016-2513: User enumeration through timing difference on password hasher work factor upgrade
+================================================================================================
+
+In each major version of Django since 1.6, the default number of iterations for
+the ``PBKDF2PasswordHasher`` and its subclasses has increased. This improves
+the security of the password as the speed of hardware increases, however, it
+also creates a timing difference between a login request for a user with a
+password encoded in an older number of iterations and login request for a
+nonexistent user (which runs the default hasher's default number of iterations
+since Django 1.6).
+
+This only affects users who haven't logged in since the iterations were
+increased. The first time a user logs in after an iterations increase, their
+password is updated with the new iterations and there is no longer a timing
+difference.
+
+The new ``BasePasswordHasher.harden_runtime()`` method allows hashers to bridge
+the runtime gap between the work factor (e.g. iterations) supplied in existing
+encoded passwords and the default work factor of the hasher. This method
+is implemented for ``PBKDF2PasswordHasher``  and ``BCryptPasswordHasher``.
+The number of rounds for the latter hasher hasn't changed since Django 1.4, but
+some projects may subclass it and increase the work factor as needed.
+
+A warning will be emitted for any :ref:`third-party password hashers that don't
+implement <write-your-own-password-hasher>` a ``harden_runtime()`` method.
+
+If you have different password hashes in your database (such as SHA1 hashes
+from users who haven't logged in since the default hasher switched to PBKDF2
+in Django 1.4), the timing difference on a login request for these users may be
+even greater and this fix doesn't remedy that difference (or any difference
+when changing hashers). You may be able to :ref:`upgrade those hashes
+<wrapping-password-hashers>` to prevent a timing attack for that case.
+
+Bugfixes
+========
+
+* Skipped URL checks (new in 1.9) if the ``ROOT_URLCONF`` setting isn't defined
+  (:ticket:`26155`).
+
+* Fixed a crash on PostgreSQL that prevented using ``TIME_ZONE=None`` and
+  ``USE_TZ=False`` (:ticket:`26177`).
+
+* Added system checks for query name clashes of hidden relationships
+  (:ticket:`26162`).
+
+* Fixed a regression for cases where
+  ``ForeignObject.get_extra_descriptor_filter()`` returned a ``Q`` object
+  (:ticket:`26153`).
+
+* Fixed regression with an ``__in=qs`` lookup for a ``ForeignKey`` with
+  ``to_field`` set (:ticket:`26196`).
+
+* Made ``forms.FileField`` and ``utils.translation.lazy_number()`` picklable
+  (:ticket:`26212`).
+
+* Fixed :class:`~django.contrib.postgres.fields.RangeField` and
+  :class:`~django.contrib.postgres.fields.ArrayField` serialization with
+  ``None`` values (:ticket:`26215`).
+
+* Fixed a crash when filtering by a ``Decimal`` in ``RawQuery``
+  (:ticket:`26219`).
+
+* Reallowed dashes in top-level domain names of URLs checked by
+  ``URLValidator`` to fix a regression in Django 1.8 (:ticket:`26204`).
+
+* Fixed some crashing deprecation shims in ``SimpleTemplateResponse`` that
+  regressed in Django 1.9 (:ticket:`26253`).
+
+* Fixed ``BoundField`` to reallow slices of subwidgets (:ticket:`26267`).
+
+* Changed the admin's "permission denied" message in the login template to use
+  ``get_username`` instead of ``username`` to support custom user models
+  (:ticket:`26231`).
+
+* Fixed a crash when passing a nonexistent template name to the cached template
+  loader's ``load_template()`` method (:ticket:`26280`).
+
+* Prevented ``ContentTypeManager`` instances from sharing their cache
+  (:ticket:`26286`).
+
+* Reverted a change in Django 1.9.2 (:ticket:`25858`) that prevented relative
+  lazy relationships defined on abstract models to be resolved according to
+  their concrete model's ``app_label`` (:ticket:`26186`).

testbed/django__django/docs/releases/1.9.6.txt

@@ -0,0 +1,32 @@
+==========================
+Django 1.9.6 release notes
+==========================
+
+*May 2, 2016*
+
+Django 1.9.6 fixes several bugs in 1.9.5.
+
+Bugfixes
+========
+
+* Added support for relative path redirects to the test client and to
+  ``SimpleTestCase.assertRedirects()`` because Django 1.9 no longer converts
+  redirects to absolute URIs (:ticket:`26428`).
+
+* Fixed ``TimeField`` microseconds round-tripping on MySQL and SQLite
+  (:ticket:`26498`).
+
+* Prevented ``makemigrations`` from generating infinite migrations for a model
+  field that references a ``functools.partial`` (:ticket:`26475`).
+
+* Fixed a regression where ``SessionBase.pop()`` returned ``None`` rather than
+  raising a ``KeyError`` for nonexistent values (:ticket:`26520`).
+
+* Fixed a regression causing the cached template loader to crash when using
+  template names starting with a dash (:ticket:`26536`).
+
+* Restored conversion of an empty string to null when saving values of
+  ``GenericIPAddressField`` on SQLite and MySQL (:ticket:`26557`).
+
+* Fixed a ``makemessages`` regression where temporary ``.py`` extensions were
+  leaked in source file paths (:ticket:`26341`).

testbed/django__django/docs/releases/1.9.9.txt

@@ -0,0 +1,15 @@
+==========================
+Django 1.9.9 release notes
+==========================
+
+*August 1, 2016*
+
+Django 1.9.9 fixes several bugs in 1.9.8.
+
+Bugfixes
+========
+
+* Fixed invalid HTML in template postmortem on the debug page
+  (:ticket:`26938`).
+
+* Fixed some GIS database function crashes on MySQL 5.7 (:ticket:`26657`).

testbed/django__django/docs/releases/2.0.10.txt

@@ -0,0 +1,32 @@
+===========================
+Django 2.0.10 release notes
+===========================
+
+*January 4, 2019*
+
+Django 2.0.10 fixes a security issue and several bugs in 2.0.9.
+
+CVE-2019-3498: Content spoofing possibility in the default 404 page
+-------------------------------------------------------------------
+
+An attacker could craft a malicious URL that could make spoofed content appear
+on the default page generated by the ``django.views.defaults.page_not_found()``
+view.
+
+The URL path is no longer displayed in the default 404 template and the
+``request_path`` context variable is now quoted to fix the issue for custom
+templates that use the path.
+
+Bugfixes
+========
+
+* Prevented repetitive calls to ``geos_version_tuple()`` in the ``WKBWriter``
+  class in an attempt to fix a random crash involving ``LooseVersion`` since
+  Django 2.0.6 (:ticket:`29959`).
+
+* Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and
+  rebuild your SQLite database if you applied a migration while using an older
+  version of Django with SQLite 3.26 or later (:ticket:`29182`).
+
+* Prevented SQLite schema alterations while foreign key checks are enabled to
+  avoid the possibility of schema corruption (:ticket:`30023`).

testbed/django__django/docs/releases/2.0.11.txt

@@ -0,0 +1,18 @@
+===========================
+Django 2.0.11 release notes
+===========================
+
+*February 11, 2019*
+
+Django 2.0.11 fixes a security issue in 2.0.10.
+
+CVE-2019-6975: Memory exhaustion in ``django.utils.numberformat.format()``
+--------------------------------------------------------------------------
+
+If ``django.utils.numberformat.format()`` -- used by ``contrib.admin`` as well
+as the ``floatformat``, ``filesizeformat``, and ``intcomma`` templates filters
+-- received a ``Decimal`` with a large number of digits or a large exponent, it
+could lead to significant memory usage due to a call to ``'{:f}'.format()``.
+
+To avoid this, decimals with more than 200 digits are now formatted using
+scientific notation.

testbed/django__django/docs/releases/2.0.12.txt

@@ -0,0 +1,12 @@
+===========================
+Django 2.0.12 release notes
+===========================
+
+*February 11, 2019*
+
+Django 2.0.12 fixes a packaging error in 2.0.11.
+
+Bugfixes
+========
+
+* Corrected packaging error from 2.0.11 (:ticket:`30175`).

testbed/django__django/docs/releases/2.0.13.txt

@@ -0,0 +1,13 @@
+===========================
+Django 2.0.13 release notes
+===========================
+
+*February 12, 2019*
+
+Django 2.0.13 fixes a regression in 2.0.12/2.0.11.
+
+Bugfixes
+========
+
+* Fixed crash in ``django.utils.numberformat.format_number()`` when the number
+  has over 200 digits (:ticket:`30177`).

testbed/django__django/docs/releases/2.0.2.txt

@@ -0,0 +1,51 @@
+==========================
+Django 2.0.2 release notes
+==========================
+
+*February 1, 2018*
+
+Django 2.0.2 fixes a security issue and several bugs in 2.0.1.
+
+CVE-2018-6188: Information leakage in ``AuthenticationForm``
+============================================================
+
+A regression in Django 1.11.8 made
+:class:`~django.contrib.auth.forms.AuthenticationForm` run its
+``confirm_login_allowed()`` method even if an incorrect password is entered.
+This can leak information about a user, depending on what messages
+``confirm_login_allowed()`` raises. If ``confirm_login_allowed()`` isn't
+overridden, an attacker enter an arbitrary username and see if that user has
+been set to ``is_active=False``. If ``confirm_login_allowed()`` is overridden,
+more sensitive details could be leaked.
+
+This issue is fixed with the caveat that ``AuthenticationForm`` can no longer
+raise the "This account is inactive." error if the authentication backend
+rejects inactive users (the default authentication backend, ``ModelBackend``,
+has done that since Django 1.10). This issue will be revisited for Django 2.1
+as a fix to address the caveat will likely be too invasive for inclusion in
+older versions.
+
+Bugfixes
+========
+
+* Fixed hidden content at the bottom of the "The install worked successfully!"
+  page for some languages (:ticket:`28885`).
+
+* Fixed incorrect foreign key nullification if a model has two foreign keys to
+  the same model and a target model is deleted (:ticket:`29016`).
+
+* Fixed regression in the use of ``QuerySet.values_list(..., flat=True)``
+  followed by ``annotate()`` (:ticket:`29067`).
+
+* Fixed a regression where a queryset that annotates with geometry objects
+  crashes (:ticket:`29054`).
+
+* Fixed a regression where ``contrib.auth.authenticate()`` crashes if an
+  authentication backend doesn't accept ``request`` and a later one does
+  (:ticket:`29071`).
+
+* Fixed a regression where ``makemigrations`` crashes if a migrations directory
+  doesn't have an ``__init__.py`` file (:ticket:`29091`).
+
+* Fixed crash when entering an invalid uuid in ``ModelAdmin.raw_id_fields``
+  (:ticket:`29094`).

testbed/django__django/docs/releases/2.0.3.txt

@@ -0,0 +1,56 @@
+==========================
+Django 2.0.3 release notes
+==========================
+
+*March 6, 2018*
+
+Django 2.0.3 fixes two security issues and several bugs in 2.0.2. Also, the
+latest string translations from Transifex are incorporated.
+
+CVE-2018-7536: Denial-of-service possibility in ``urlize`` and ``urlizetrunc`` template filters
+===============================================================================================
+
+The ``django.utils.html.urlize()`` function was extremely slow to evaluate
+certain inputs due to catastrophic backtracking vulnerabilities in two regular
+expressions. The ``urlize()`` function is used to implement the ``urlize`` and
+``urlizetrunc`` template filters, which were thus vulnerable.
+
+The problematic regular expressions are replaced with parsing logic that
+behaves similarly.
+
+CVE-2018-7537: Denial-of-service possibility in ``truncatechars_html`` and ``truncatewords_html`` template filters
+==================================================================================================================
+
+If ``django.utils.text.Truncator``'s ``chars()`` and ``words()`` methods were
+passed the ``html=True`` argument, they were extremely slow to evaluate certain
+inputs due to a catastrophic backtracking vulnerability in a regular
+expression. The ``chars()`` and ``words()`` methods are used to implement the
+``truncatechars_html`` and ``truncatewords_html`` template filters, which were
+thus vulnerable.
+
+The backtracking problem in the regular expression is fixed.
+
+Bugfixes
+========
+
+* Fixed a regression that caused sliced ``QuerySet.distinct().order_by()``
+  followed by ``count()`` to crash (:ticket:`29108`).
+
+* Prioritized the datetime and time input formats without ``%f`` for the Thai
+  locale to fix the admin time picker widget displaying "undefined"
+  (:ticket:`29109`).
+
+* Fixed crash with ``QuerySet.order_by(Exists(...))`` (:ticket:`29118`).
+
+* Made ``Q.deconstruct()`` deterministic with multiple keyword arguments
+  (:ticket:`29125`). You may need to modify ``Q``'s in existing migrations, or
+  accept an autogenerated migration.
+
+* Fixed a regression where a ``When()`` expression with a list argument crashes
+  (:ticket:`29166`).
+
+* Fixed crash when using a ``Window()`` expression in a subquery
+  (:ticket:`29172`).
+
+* Fixed ``AbstractBaseUser.normalize_username()`` crash if the ``username``
+  argument isn't a string (:ticket:`29176`).

testbed/django__django/docs/releases/2.0.4.txt

@@ -0,0 +1,34 @@
+==========================
+Django 2.0.4 release notes
+==========================
+
+*April 2, 2018*
+
+Django 2.0.4 fixes several bugs in 2.0.3.
+
+Bugfixes
+========
+
+* Fixed a crash when filtering with an ``Exists()`` annotation of a queryset
+  containing a single field (:ticket:`29195`).
+
+* Fixed admin autocomplete widget's translations for ``zh-hans`` and
+  ``zh-hant`` languages (:ticket:`29213`).
+
+* Corrected admin's autocomplete widget to add a space after custom classes
+  (:ticket:`29221`).
+
+* Fixed ``PasswordResetConfirmView`` crash when using a user model with a
+  ``UUIDField`` primary key and the reset URL contains an encoded primary key
+  value that decodes to an invalid UUID (:ticket:`29206`).
+
+* Fixed a regression in Django 1.11.8 where combining two annotated
+  ``values_list()`` querysets with ``union()``, ``difference()``, or
+  ``intersection()`` crashed due to mismatching columns (:ticket:`29229`).
+
+* Fixed a regression in Django 1.11 where an empty choice could be initially
+  selected for the ``SelectMultiple`` and ``CheckboxSelectMultiple`` widgets
+  (:ticket:`29273`).
+
+* Fixed a regression in Django 2.0 where ``OpenLayersWidget`` deserialization
+  ignored the widget map's SRID and assumed 4326 (WGS84) (:ticket:`29116`).

testbed/django__django/docs/releases/2.0.6.txt

@@ -0,0 +1,25 @@
+==========================
+Django 2.0.6 release notes
+==========================
+
+*June 1, 2018*
+
+Django 2.0.6 fixes several bugs in 2.0.5.
+
+Bugfixes
+========
+
+* Fixed a regression that broke custom template filters that use decorators
+  (:ticket:`29400`).
+
+* Fixed detection of custom URL converters in included patterns
+  (:ticket:`29415`).
+
+* Fixed a regression that added an unnecessary subquery to the ``GROUP BY``
+  clause on MySQL when using a ``RawSQL`` annotation (:ticket:`29416`).
+
+* Fixed ``WKBWriter.write()`` and ``write_hex()`` for empty polygons on
+  GEOS 3.6.1+ (:ticket:`29460`).
+
+* Fixed a regression in Django 1.10 that could result in large memory usage
+  when making edits using ``ModelAdmin.list_editable`` (:ticket:`28462`).

testbed/django__django/docs/releases/2.0.7.txt

@@ -0,0 +1,21 @@
+==========================
+Django 2.0.7 release notes
+==========================
+
+*July 2, 2018*
+
+Django 2.0.7 fixes several bugs in 2.0.6.
+
+Bugfixes
+========
+
+* Fixed admin changelist crash when using a query expression without ``asc()``
+  or ``desc()`` in the page's ordering (:ticket:`29428`).
+
+* Fixed admin check crash when using a query expression in
+  ``ModelAdmin.ordering`` (:ticket:`29428`).
+
+* Fixed ``__regex`` and ``__iregex`` lookups with MySQL 8 (:ticket:`29451`).
+
+* Fixed migrations crash with namespace packages on Python 3.7
+  (:ticket:`28814`).

testbed/django__django/docs/releases/2.0.8.txt

@@ -0,0 +1,29 @@
+==========================
+Django 2.0.8 release notes
+==========================
+
+*August 1, 2018*
+
+Django 2.0.8 fixes a security issue and several bugs in 2.0.7.
+
+CVE-2018-14574: Open redirect possibility in ``CommonMiddleware``
+=================================================================
+
+If the :class:`~django.middleware.common.CommonMiddleware` and the
+:setting:`APPEND_SLASH` setting are both enabled, and if the project has a
+URL pattern that accepts any path ending in a slash (many content management
+systems have such a pattern), then a request to a maliciously crafted URL of
+that site could lead to a redirect to another site, enabling phishing and other
+attacks.
+
+``CommonMiddleware`` now escapes leading slashes to prevent redirects to other
+domains.
+
+Bugfixes
+========
+
+* Fixed a regression in Django 2.0.7 that broke the ``regex`` lookup on MariaDB
+  (even though MariaDB isn't officially supported) (:ticket:`29544`).
+
+* Fixed a regression where ``django.template.Template`` crashed if the
+  ``template_string`` argument is lazy (:ticket:`29617`).

testbed/django__django/docs/releases/2.0.9.txt

@@ -0,0 +1,13 @@
+==========================
+Django 2.0.9 release notes
+==========================
+
+*October 1, 2018*
+
+Django 2.0.9 fixes a data loss bug in 2.0.8.
+
+Bugfixes
+========
+
+* Fixed a race condition in ``QuerySet.update_or_create()`` that could result
+  in data loss (:ticket:`29499`).

testbed/django__django/docs/releases/2.1.1.txt

@@ -0,0 +1,51 @@
+==========================
+Django 2.1.1 release notes
+==========================
+
+*August 31, 2018*
+
+Django 2.1.1 fixes several bugs in 2.1.
+
+Bugfixes
+========
+
+* Fixed a race condition in ``QuerySet.update_or_create()`` that could result
+  in data loss (:ticket:`29499`).
+
+* Fixed a regression where ``QueryDict.urlencode()`` crashed if the dictionary
+  contains a non-string value (:ticket:`29627`).
+
+* Fixed a regression in Django 2.0 where using ``manage.py test --keepdb``
+  fails on PostgreSQL if the database exists and the user doesn't have
+  permission to create databases (:ticket:`29613`).
+
+* Fixed a regression in Django 2.0 where combining ``Q`` objects with ``__in``
+  lookups and lists crashed (:ticket:`29643`).
+
+* Fixed translation failure of ``DurationField``'s "overflow" error message
+  (:ticket:`29623`).
+
+* Fixed a regression where the admin change form crashed if the user doesn't
+  have the 'add' permission to a model that uses ``TabularInline``
+  (:ticket:`29637`).
+
+* Fixed a regression where a ``related_query_name`` reverse accessor wasn't set
+  up when a ``GenericRelation`` is declared on an abstract base model
+  (:ticket:`29653`).
+
+* Fixed the test client's JSON serialization of a request data dictionary for
+  structured content type suffixes (:ticket:`29662`).
+
+* Made the admin change view redirect to the changelist view after a POST if
+  the user has the 'view' permission (:ticket:`29663`).
+
+* Fixed admin change view crash for view-only users if the form has an extra
+  form field (:ticket:`29682`).
+
+* Fixed a regression in Django 2.0.5 where ``QuerySet.values()`` or
+  ``values_list()`` after combining querysets with ``extra()`` with
+  ``union()``, ``difference()``, or ``intersection()`` crashed due to
+  mismatching columns (:ticket:`29694`).
+
+* Fixed crash if ``InlineModelAdmin.has_add_permission()`` doesn't accept the
+  ``obj`` argument (:ticket:`29723`).

testbed/django__django/docs/releases/2.1.11.txt

@@ -0,0 +1,57 @@
+===========================
+Django 2.1.11 release notes
+===========================
+
+*August 1, 2019*
+
+Django 2.1.11 fixes security issues in 2.1.10.
+
+CVE-2019-14232: Denial-of-service possibility in ``django.utils.text.Truncator``
+================================================================================
+
+If ``django.utils.text.Truncator``'s ``chars()`` and ``words()`` methods
+were passed the ``html=True`` argument, they were extremely slow to evaluate
+certain inputs due to a catastrophic backtracking vulnerability in a regular
+expression. The ``chars()`` and ``words()`` methods are used to implement the
+:tfilter:`truncatechars_html` and :tfilter:`truncatewords_html` template
+filters, which were thus vulnerable.
+
+The regular expressions used by ``Truncator`` have been simplified in order to
+avoid potential backtracking issues. As a consequence, trailing punctuation may
+now at times be included in the truncated output.
+
+CVE-2019-14233: Denial-of-service possibility in ``strip_tags()``
+=================================================================
+
+Due to the behavior of the underlying ``HTMLParser``,
+:func:`django.utils.html.strip_tags` would be extremely slow to evaluate
+certain inputs containing large sequences of nested incomplete HTML entities.
+The ``strip_tags()`` method is used to implement the corresponding
+:tfilter:`striptags` template filter, which was thus also vulnerable.
+
+``strip_tags()`` now avoids recursive calls to ``HTMLParser`` when progress
+removing tags, but necessarily incomplete HTML entities, stops being made.
+
+Remember that absolutely NO guarantee is provided about the results of
+``strip_tags()`` being HTML safe. So NEVER mark safe the result of a
+``strip_tags()`` call without escaping it first, for example with
+:func:`django.utils.html.escape`.
+
+CVE-2019-14234: SQL injection possibility in key and index lookups for ``JSONField``/``HStoreField``
+====================================================================================================
+
+:lookup:`Key and index lookups <jsonfield.key>` for
+``django.contrib.postgres.fields.JSONField`` and :lookup:`key lookups
+<hstorefield.key>` for :class:`~django.contrib.postgres.fields.HStoreField`
+were subject to SQL injection, using a suitably crafted dictionary, with
+dictionary expansion, as the ``**kwargs`` passed to ``QuerySet.filter()``.
+
+CVE-2019-14235: Potential memory exhaustion in ``django.utils.encoding.uri_to_iri()``
+=====================================================================================
+
+If passed certain inputs, :func:`django.utils.encoding.uri_to_iri` could lead
+to significant memory usage due to excessive recursion when re-percent-encoding
+invalid UTF-8 octet sequences.
+
+``uri_to_iri()`` now avoids recursion when re-percent-encoding invalid UTF-8
+octet sequences.

testbed/django__django/docs/releases/2.1.13.txt

@@ -0,0 +1,14 @@
+===========================
+Django 2.1.13 release notes
+===========================
+
+*October 1, 2019*
+
+Django 2.1.13 fixes a regression in 2.1.11.
+
+Bugfixes
+========
+
+* Fixed a crash when filtering with a ``Subquery()`` annotation of a queryset
+  containing ``django.contrib.postgres.fields.JSONField`` or
+  :class:`~django.contrib.postgres.fields.HStoreField` (:ticket:`30769`).