django-queuebie 0.3.9__tar.gz → 0.4.0__tar.gz

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/.ambient-package-update/metadata.py

@@ -4,6 +4,7 @@ from ambient_package_update.metadata.constants import (
     DEV_DEPENDENCIES,
     LICENSE_MIT,
     SUPPORTED_DJANGO_VERSIONS,
+    SUPPORTED_PYTHON_VERSIONS,
 )
 from ambient_package_update.metadata.maintainer import PackageMaintainer
 from ambient_package_update.metadata.package import PackageMetadata
@@ -33,12 +34,7 @@ METADATA = PackageMetadata(
         f"Django>={SUPPORTED_DJANGO_VERSIONS[0]}",
     ],
     supported_django_versions=SUPPORTED_DJANGO_VERSIONS,
-    supported_python_versions=[
-        "3.10",
-        "3.11",
-        "3.12",
-        "3.13",
-    ],
+    supported_python_versions=SUPPORTED_PYTHON_VERSIONS,
     optional_dependencies={
         "dev": [
             *DEV_DEPENDENCIES,

django_queuebie-0.4.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Report a problem to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To reproduce
+
+Steps to reproduce the behavior:
+
+1. ...
+2. ...
+3. ...
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Environment
+
+- `django-queuebie` version:
+- Python version:
+- Django version:
+- Operating system:
+
+## Additional context
+
+Add any other context, tracebacks, or screenshots about the problem here.

django_queuebie-0.4.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/ambient-innovation/django-queuebie/security/advisories/new
+    about: Please report security issues privately via a security advisory, not as a public issue.

django_queuebie-0.4.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+## Is your feature request related to a problem?
+
+A clear and concise description of what the problem is. Ex. I'm always
+frustrated when [...]
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+## Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've
+considered.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

django_queuebie-0.4.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+## Description
+
+Please include a summary of the change and which issue is fixed (if any).
+
+Fixes #(issue)
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+
+## Checklist
+
+- [ ] My code follows the style guidelines of this project (linting passes)
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have updated the documentation where necessary
+- [ ] I have added an entry to `CHANGES.md`
+- [ ] I have bumped the version in `queuebie/__init__.py`

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/.github/workflows/quality-gate.yml

@@ -9,10 +9,10 @@ jobs:
     steps:
       - uses: actions/checkout@v6
 
-      - name: Set up Python 3.13
+      - name: Set up Python 3.14
         uses: actions/setup-python@v6
         with:
-          python-version: "3.13"
+          python-version: "3.14"
 
       - name: Install required packages
         run: pip install pre-commit
@@ -25,18 +25,19 @@ jobs:
     runs-on: ubuntu-24.04
     strategy:
       matrix:
-        python-version: ['3.10', '3.11', '3.12', '3.13', ]
+        python-version: ['3.11', '3.12', '3.13', '3.14', ]
         django-version: ['42', '52', '60', ]
 
+        # Exclude Python/Django combinations that are not supported upstream.
         exclude:
           - python-version: '3.11'
             django-version: 60
-          - python-version: '3.10'
-            django-version: 60
-          - python-version: '3.9'
-            django-version: 52
-          - python-version: "3.13"
+          - python-version: '3.13'
+            django-version: 42
+          - python-version: '3.14'
             django-version: 42
+          - python-version: '3.14'
+            django-version: 52
 
     steps:
       - uses: actions/checkout@v6
@@ -46,6 +47,8 @@ jobs:
           python-version: ${{ matrix.python-version }}
       - name: Install uv
         uses: astral-sh/setup-uv@v8.0.0
+        with:
+          cache-suffix: ${{ github.ref_type }}
       - name: Install tox
         run: uv pip install --system tox tox-uv
       - name: Run Tests
@@ -69,7 +72,7 @@ jobs:
 
       - uses: actions/setup-python@v6
         with:
-          python-version: '3.13'
+          python-version: '3.14'
 
       - name: Install dependencies
         run: python -m pip install --upgrade coverage[toml]

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/.github/workflows/release.yml

@@ -13,19 +13,40 @@ jobs:
   ci:
     uses: ./.github/workflows/quality-gate.yml
 
+  check-branch:
+    name: Verify tag is on main
+    runs-on: ubuntu-24.04
+    outputs:
+      on-main: ${{ steps.check.outputs.on-main }}
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - name: Check if tag is on main
+        id: check
+        run: |
+          git fetch origin main
+          if git merge-base --is-ancestor "${{ github.sha }}" origin/main; then
+            echo "on-main=true" >> $GITHUB_OUTPUT
+          else
+            echo "Tag is not on main, skipping release." >&2
+            echo "on-main=false" >> $GITHUB_OUTPUT
+          fi
+
   build:
     name: Build distribution packages
     runs-on: ubuntu-24.04
-    needs: ci
+    needs: [ci, check-branch]
+    if: needs.check-branch.outputs.on-main == 'true'
     permissions:
       contents: read
     steps:
       - uses: actions/checkout@v6
 
-      - name: Set up Python 3.13
+      - name: Set up Python 3.14
         uses: actions/setup-python@v6
         with:
-          python-version: "3.13"
+          python-version: "3.14"
 
       - name: Install uv
         uses: astral-sh/setup-uv@v8.0.0

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/.pre-commit-config.yaml

@@ -23,7 +23,7 @@ repos:
     rev: v3.21.2
     hooks:
       - id: pyupgrade
-        args: [ --py310-plus ]
+        args: [ --py311-plus ]
 
   - repo: https://github.com/adamchainz/django-upgrade
     rev: 1.30.0

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/.readthedocs.yaml

@@ -9,7 +9,7 @@ version: 2
 build:
   os: ubuntu-24.04
   tools:
-    python: "3.13"
+    python: "3.14"
 
 # Build documentation in the "docs/" directory with Sphinx
 sphinx:
@@ -21,11 +21,13 @@ sphinx:
 #    - epub
 
 # Optional but recommended, declare the Python requirements required
-# to build your documentation
-# See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
+# to build your documentation.
+# Read the Docs supports uv natively, so we let it sync the project with the
+# "dev" extra (which contains the documentation dependencies).
+# See https://docs.readthedocs.com/platform/en/stable/config-file/v2.html#python-install
 python:
   install:
-    - method: pip
-      path: .
-      extra_requirements:
+    - method: uv
+      command: sync
+      extras:
         - dev

django_queuebie-0.4.0/CHANGES.md

@@ -0,0 +1,53 @@
+# Changelog
+
+**0.4.0** (2026-07-03)
+  * **Breaking change:** Dropped support for Python 3.10 (nearing end-of-life in October 2026)
+  * Added support for Python 3.14
+  * Added native uv support to the rendered Read the Docs configuration
+  * Replaced the unmaintained "m2r2" documentation dependency with "sphinx-mdinclude"
+  * Added a Code of Conduct, issue templates and a pull request template to rendered packages
+  * Made the single-version CI and Read the Docs jobs track the newest supported Python version
+  * Bumped rendered single-version jobs to Python 3.14
+  * Added a cache suffix to the uv setup step to avoid CI cache namespace conflicts
+  * Excluded unsupported Python/Django combinations (Python 3.14 with Django 4.2 and 5.2) from the rendered CI matrix
+  * Fixed the rendered ruff target-version to track the minimum supported Python (matching requires-python) instead of the newest
+  * Removed the stale .md source suffix from the rendered Sphinx config, since sphinx-mdinclude provides only the mdinclude directive (not a Markdown source parser)
+
+**0.3.10** (2026-03-30)
+  * Maintenance updates via ambient-package-update
+
+**0.3.9** (2026-03-30)
+  * Maintenance updates via ambient-package-update
+
+**0.3.8** (2025-12-11)
+  * Maintenance updates via ambient-package-update
+
+**0.3.7** (2025-10-15)
+  * Maintenance updates via ambient-package-update
+
+**0.3.6** (2025-10-10)
+  * Maintenance updates via ambient-package-update
+
+**0.3.5** (2025-10-09)
+  * Maintenance updates via ambient-package-update
+
+**0.3.4** (2025-05-29)
+  * Maintenance updates via ambient-package-update
+
+**0.3.3** (2025-04-03)
+  * Clarified package tagline
+
+**0.3.2** (2025-04-03)
+  * Maintenance updates via ambient-package-update
+
+* *0.3.1* (2025-03-19)
+  * Added a paranoid-ish test to check that the import logic isn't breaking any testing functionality
+
+* *0.3.0* (2025-03-19)
+  * The whole queue iteration now is wrapped in a transaction atomic
+
+* *0.2.0* (2025-03-17)
+  * Extend strict mode to prohibit event (!) handlers to talk to the database
+
+* *0.1.0* (2025-01-29)
+  * Project init

django_queuebie-0.4.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+hello@ambient.digital.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: django-queuebie
-Version: 0.3.9
+Version: 0.4.0
 Summary: A simple and synchronous message queue for commands and events for Django
 Project-URL: Homepage, https://github.com/ambient-innovation/django-queuebie/
 Project-URL: Documentation, https://django-queuebie.readthedocs.io/en/latest/index.html
@@ -43,21 +43,21 @@ Classifier: Natural Language :: English
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Utilities
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 Requires-Dist: django>=4.2
 Provides-Extra: dev
 Requires-Dist: ambient-package-update; extra == 'dev'
 Requires-Dist: keyring~=25.7; extra == 'dev'
-Requires-Dist: m2r2~=0.3; extra == 'dev'
 Requires-Dist: pre-commit~=4.3; extra == 'dev'
 Requires-Dist: pytest-cov~=7.0; extra == 'dev'
 Requires-Dist: pytest-django~=4.11; extra == 'dev'
 Requires-Dist: pytest-mock~=3.15; extra == 'dev'
+Requires-Dist: sphinx-mdinclude~=0.6; extra == 'dev'
 Requires-Dist: sphinx-rtd-theme~=3.0; extra == 'dev'
 Requires-Dist: sphinx~=7.4; extra == 'dev'
 Requires-Dist: typer~=0.19; extra == 'dev'

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/docs/conf.py

@@ -36,7 +36,7 @@ from queuebie import __version__  # noqa: E402
 # -- Project information -----------------------------------------------------
 
 project = "django-queuebie"
-copyright = "2026, Ambient Innovation: GmbH"  # noqa: A001
+copyright = "2026, Beyonder Deutschland"  # noqa: A001
 author = "Ambient Digital <hello@ambient.digital>"
 version = __version__
 release = __version__
@@ -49,10 +49,10 @@ release = __version__
 extensions = [
     "sphinx_rtd_theme",
     "sphinx.ext.autodoc",
-    "m2r2",
+    "sphinx_mdinclude",
 ]
 
-source_suffix = [".rst", ".md"]
+source_suffix = [".rst"]
 
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ["_templates"]

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/pyproject.toml

@@ -21,16 +21,16 @@ classifiers = [
     "Operating System :: OS Independent",
     "Programming Language :: Python",
     "Programming Language :: Python :: 3",
-    "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
     "Topic :: Utilities",
 ]
 dynamic = ["version"]
 description = "A simple and synchronous message queue for commands and events for Django"
 license = {"file" = "LICENSE.md"}
-requires-python = ">=3.10"
+requires-python = ">=3.11"
 dependencies = [
     'Django>=4.2',
 ]
@@ -44,7 +44,7 @@ dev = [
    'pre-commit~=4.3',
    'sphinx~=7.4',
    'sphinx-rtd-theme~=3.0',
-   'm2r2~=0.3',
+   'sphinx-mdinclude~=0.6',
    'uv~=0.9',
    'keyring~=25.7',
    'ambient-package-update',
@@ -156,8 +156,8 @@ line-length = 120
 # Allow unused variables when underscore-prefixed.
 lint.dummy-variable-rgx = "^(_+|(_+[a-zA-Z0-9_]*[a-zA-Z0-9]+?))$"
 
-# Assume Python 3.13
-target-version = "py313"
+# Match the minimum supported Python version (mirrors requires-python above)
+target-version = "py311"
 
 [tool.ruff.format]
 # Like Black, use double quotes for strings.
@@ -218,10 +218,10 @@ deps = ["Django==5.2.*"]
 deps = ["Django==6.0.*"]
 
 [tool.tox.gh_actions.python]
-"3.10" = "py310"
 "3.11" = "py311"
 "3.12" = "py312"
 "3.13" = "py313"
+"3.14" = "py314"
 
 [tool.pytest.ini_options]
 python_files = [

{django_queuebie-0.3.9 → django_queuebie-0.4.0}/queuebie/__init__.py

@@ -1,6 +1,6 @@
 """A simple and synchronous message queue for commands and events for Django"""
 
-__version__ = "0.3.9"
+__version__ = "0.4.0"
 
 from queuebie.registry import MessageRegistry