Packages changed:
  ibus-m17n (1.4.13 -> 1.4.17)
  python-SQLAlchemy (1.4.40 -> 1.4.41)
  python-charset-normalizer (2.1.0 -> 2.1.1)
  python-idna (3.3 -> 3.4)
  python-regex (2022.9.11 -> 2022.9.13)

=== Details ===

==== ibus-m17n ====
Version update (1.4.13 -> 1.4.17)

update: 1.4.13 -> 1.4.17
- Fix problem that sa-IAST input method cannot be activated and make settings of sa-IAST work
  * https://github.com/ibus/ibus-m17n/issues/52
- Let IBusM17nEngine inherit from IBusEngineSimple to enable compose support
  * https://github.com/ibus/ibus-m17n/issues/51

==== python-SQLAlchemy ====
Version update (1.4.40 -> 1.4.41)

- update to 1.4.41:
  * Fixed issue where use of the :func:`_sql.table` construct, passing a string
    for the :paramref:`_sql.table.schema` parameter, would fail to take the
    "schema" string into account when producing a cache key, thus leading to
    caching collisions if multiple, same-named :func:`_sql.table` constructs
    with different schemas were used.
  * Fixed event listening issue where event listeners added to a superclass
    would be lost if a subclass were created which then had its own listeners
    associated. The practical example is that of the :class:`.sessionmaker`
    class created after events have been associated with the
    :class:`_orm.Session` class.
  * Hardened the cache key strategy for the :func:`_orm.aliased` and
    :func:`_orm.with_polymorphic` constructs. While no issue involving actual
    statements being cached can easily be demonstrated (if at all), these two
    constructs were not including enough of what makes them unique in their
    cache keys for caching on the aliased construct alone to be accurate.
  * Fixed regression appearing in the 1.4 series where a joined-inheritance
    query placed as a subquery within an enclosing query for that same entity
    would fail to render the JOIN correctly for the inner query. The issue
    manifested in two different ways prior and subsequent to version 1.4.18
    (related issue :ticket:`6595`), in one case rendering JOIN twice, in the
    other losing the JOIN entirely. To resolve, the conditions under which
    "polymorphic loading" are applied have been scaled back to not be invoked
    for simple joined inheritance queries.
  * Fixed issue in :mod:`sqlalchemy.ext.mutable` extension where collection
    links to the parent object would be lost if the object were merged with
    :meth:`.Session.merge` while also passing :paramref:`.Session.merge.load`
    as False.
  * Fixed issue involving :func:`_orm.with_loader_criteria` where a closure
    variable used as bound parameter value within the lambda would not carry
    forward correctly into additional relationship loaders such as
    :func:`_orm.selectinload` and :func:`_orm.lazyload` after the statement
    were cached, using the stale originally-cached value instead.
  * Fixed regression caused by the fix for :ticket:`8231` released in 1.4.40
    where connection would fail if the user did not have permission to query
    the ``dm_exec_sessions`` or ``dm_pdw_nodes_exec_sessions`` system views
    when trying to determine the current transaction isolation level.
  * Integrated support for asyncpg's ``terminate()`` method call for cases
    where the connection pool is recycling a possibly timed-out connection,
    where a connection is being garbage collected that wasn't gracefully

==== python-charset-normalizer ====
Version update (2.1.0 -> 2.1.1)

- update to 2.1.1:
  * Function `normalize` scheduled for removal in 3.0
  * Removed useless call to decode in fn is_unprintable (#206)

==== python-idna ====
Version update (3.3 -> 3.4)

- update to 3.4:
  * Update to Unicode 15.0.0
  * Migrate to pyproject.toml for build information (PEP 621)
  * Correct another instance where generic exception was raised instead of
    IDNAError for malformed input
  * Source distribution uses zeroized file ownership for improved
    reproducibility

==== python-regex ====
Version update (2022.9.11 -> 2022.9.13)

- update to 2022.9.13:
  * update to unicode 15.0