RepoJournal
Arch Linux

@archlinux

The Arch Linux org — the rolling distro and the developers who run it

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

ARCHWEB SHIPS DJANGO NINJA API LAYER WITH RELENG RELEASES ENDPOINT

By RepoJournal · Filed · About Arch Linux

Arch's web infrastructure is now exposing structured release data through a modern REST API with full OpenAPI documentation and Swagger UI.

The archweb project merged a significant architectural addition [1] that introduces Django Ninja at /api/ with the first production endpoint serving release data. This closes the door on a longstanding issue by providing machine-readable access to Arch releases through a Pydantic-backed schema that mirrors the existing JSON encoder output. The new API includes 10 tests covering endpoint behavior and OpenAPI contract compliance, plus RFC 8594 deprecation header support for managing future breaking changes. On the tooling side, the project is tightening its type safety posture [3] by adding mypy configuration and actively silencing warnings [2] to run a fully typechecked codebase. Ruff bumped to 0.15.17 [4] brings human-readable suppression comment names in preview, making it easier to annotate intentional violations. Core packages are rolling forward: sudo to 1.9.17.p2-3 in testing [5], pambase with a date-based version bump [6], and pytest-retry, deepin-voice-note, and update all seeing incremental point releases across extra [7] [8] [9].

Action items

References

  1. [1] feat(api): add Django Ninja with releng releases endpoint ↗ archlinux/archweb
  2. [2] devel: Drop partial typing to silence mypy warning archlinux/archweb
  3. [3] pyproject: Add mypy configuration archlinux/archweb
  4. [4] build(deps-dev): bump ruff from 0.15.15 to 0.15.17 ↗ archlinux/archweb
  5. [5] update sudo to 1.9.17.p2-3 in core-testing-x86_64 archlinux/state
  6. [6] update pambase to 20260616-1 in core-testing-any archlinux/state
  7. [7] update marked to 9.1.4-1 in extra-any archlinux/state
  8. [8] update deepin-voice-note to 6.5.41-1 in extra-x86_64 archlinux/state
  9. [9] update python-pytest-retry to 1.7.0-1 in extra-any archlinux/state

FAQ

What changed in Arch Linux on June 16, 2026?
Arch's web infrastructure is now exposing structured release data through a modern REST API with full OpenAPI documentation and Swagger UI.
What should Arch Linux teams do about it?
Review /api/v1/releng/releases/ endpoint for production readiness • Run mypy locally to verify type coverage after latest configuration • Test sudo 1.9.17.p2-3 from core-testing before rolling to core
Which Arch Linux repositories shipped on June 16, 2026?
archlinux/archweb, archlinux/state

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.