pkg-vulnerabilities: add last 12 hours CVEs
+ libtasn1 (possible patch under review),
lmdb (shared via fulldisclosure ML, unclear if shared upstream or not,
probably not fixed),
py-urllib3
py-test-doctestplus: updated to 1.7.0
1.7.0 (2026-01-07)
- Fixing crashing sphinx builds where multiple directives are used with the
first one expecting content. The order of the directives used does not
matter after this fix.
- Versions of Python <3.10 and pytest<7 are no longer supported.
py-test-datafiles: updated to 3.0.1
3.0.1
Fixed
* Corrected minimum pytest version requirement from >=3.6 to >=6.2.0 to match actual requirements (tmp_path fixture)
* Closed issue 11 - file mode bits are now preserved (resolved by pathlib migration in 3.0)
Added
* Regression test to ensure file permissions are preserved when copying files
Changed
* Migrated to uv for package management and builds
* Added ruff for code formatting and linting
* Converted documentation from RST to Markdown
* Added Dependabot for automated dependency updates
* Updated GitHub Actions workflows for CI/CD
py-asdf: updated to 5.1.0
5.1.0 (2025-11-06)
Bugfix
- Fix but preventing extension checking when opening a file with lazy_tree
enabled.
Feature
- Add support for registering unstable/development versions of core extensions
if the ASDF_UNSTABLE_CORE_SCHEMAS environment variable is set.
Writing files with unstable/development extensions is discouraged as schema
changes may make these files unreable in the future.
- Add ``warn_on_failed_conversion`` to ``AsdfConfig``.
Enabling this option will convert any exceptions raised during conversion to
warnings.
[15 lines not shown]
py-asdf-standard: updated to 1.4.0
1.4.0 (2025-08-27)
- Update documentation to use new terminology. The
ASDF specification refers to the description of the file
format whereas the ASDF core schemas refers to the versioned
collection of schemas for core objects (ndarray, software, etc)
- Add datatype-1.0.0 schema
- Add galexsec time to time-1.4.0
py-flask-security: updated to 5.7.1
Version 5.7.1
Fixes
- (:issue:`1147`) Regression when updating hash algorithm from bcrypt (willcroft)
Version 5.7.0
This release contains a set of small backward incompatible changes. Please read these notes carefully.
Features & Improvements
- (:pr:`1132`) Add Arabic translations (samialfattani)
- (:issue:`1123`) Enable forgot-password workflow for authenticated users.
Fixes
[39 lines not shown]
py-anyio: updated to 4.12.1
4.12.1
- Changed all functions currently raising the private ``NoCurrentAsyncBackend``
exception (since v4.12.0) to instead raise the public ``NoEventLoopError`` exception
- Fixed ``anyio.functools.lru_cache`` not working with instance methods
py-notebook: updated to 7.5.1
7.5.1
Bugs fixed
- Fix selector for the `O` keyboard shortcut
- Fix missing debugger display provider in Notebook
Maintenance and upkeep improvements
- Update to JupyterLab v4.5.1
- Fix link to the IPython install page
- Fix `hatch build`, ignore links to `blog.jupyter.org`
- Bump the actions group with 4 updates
py-cares: update to 5.0.1.
5.0.1
What's Changed
Fix IDNA 2008 test by @saghul in #288
5.0.0
What's Changed
Use Literal for type by @Dreamsorcerer in #263
Use CMake for compiling c-ares by @saghul in #267
build(deps): bump actions/setup-python from 5 to 6 by @dependabot[bot] in #265
build(deps): bump pypa/cibuildwheel from 3.1.4 to 3.2.0 by @dependabot[bot] in #264
Move project metadata to pyproject.toml by @saghul in #268
Remove gethostbyname by @saghul in #270
Remove getsock by @saghul in #271
[13 lines not shown]
py-numpy: update to 2.4.0.
NumPy 2.4.0 released
20 Dec, 2025 – The NumPy 2.4.0 release continues the work to improve
free threaded Python support, user dtypes implementation, and
annotations. There are many expired deprecations and bug fixes as
well. Highlights are:
Many annotation improvements. In particular, runtime signature introspection.
New casting kwarg 'same_value' for casting by value.
New PyUFunc_AddLoopsFromSpec function that can be used to add user sort loops using the ArrayMethod API.
New __numpy_dtype__ protocol.
This release supports Python versions 3.11-3.14
alsa-lib: update to 1.2.15.1.
1.12.5.1
alsa-lib
Core
Release v1.2.15.1
ucm: use closefrom instead of close_range
Use Case Manager API
ucm: exec - fix maxfd used warning
ucm: use closefrom instead of close_range
Configuration
conf: cards: unify whitespace - use tabs and remove trailing spaces
conf: pistachio-card: define pcm configuration block only one time
[189 lines not shown]
py-lazr.config: updated to 3.1
3.1 (2024-12-09)
- Add support for Python 3.12 and 3.13.
- Remove support for Python 3.7 and below.
3.0 (2023-04-08)
- Add basic pre-commit configuration.
- Publish Documentation on Read the Docs.
- Apply inclusive naming via the woke pre-commit hook.
- Test using ``zope.testrunner`` rather than ``nose``.
- Officially add support for Python 3.9, 3.10 and 3.11.
- Drop support for Python 2.6, 2.7, and 3.4.
- Apply ``black`` and ``isort``.
py-lazr.delegates: updated to 2.1.1
2.1.1 (2024-12-05)
- Add support for Python 3.12 and 3.13.
- Drop support for Python 3.5, 3.6 and 3.7.
2.1.0 (2023-03-20)
- Officially add support for Python 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11.
- Drop support for Python 2, 3.2, 3.3, and 3.4.
- Test using ``zope.testrunner`` rather than ``nose``.
- Bring coverage to 100%.
- Switch to declarative ``setuptools`` configuration.
- Add linters.
- Fix the `woke` linter.
py-peewee: updated to 3.19.0
3.19.0
* Move to new build system using pyproject and github actions.
* No longer build and ship the Sqlite C extensions by default. Users who prefer
to use those can install via the sdist `pip install peewee --no-binary :all:`.
Rationale about the Sqlite C extensions -- I've started shipping pysqlite3 as a
statically-linked, self-contained binary wheel. This means that when using
Peewee with the statically-linked pysqlite3, you can end up in a funny
situation where the peewee Sqlite extensions are linked against the system
libsqlite3, and the pysqlite driver has it's own Sqlite embedded, which does
not work.
If you are using the system/standard-lib sqlite3 module then the extension
works properly, because everything is talking to the same `libsqlite3`.
Similarly if you built pysqlite3 to link against the system `libsqlite3`
[22 lines not shown]
