Bump django-modern-rpc from 1.1.0 to 2.1.0

[dependabot]

Bumps django-modern-rpc from 1.1.0 to 2.1.0.

Release notes

Sourced from django-modern-rpc's releases.

v2.1.0 (2026-06-05)

Improvements

• A new JSON-RPC backend based on the third party library ujson has been added.
• It is now possible to call a procedure without the "params" argument in a multicall request.

Breaking Changes

• AuthenticationError now uses a dedicated error code (-32098) instead of the generic internal error code (-32603). Clients relying on the error code to detect authentication failures should update their checks accordingly.

Misc

• Dropped support for Django < 4.2
• Dropped support for Python < 3.10

v2.0.0 (2025-11-10)

Improvements

• The new API, heavily inspired from tools like FastAPI or django-ninja, encapsulate the procedures registration in a dedicated RpcServer instance. This removes the need to lookup modules based on settings.MODERNRPC_METHODS_MODULES value, so modernrpc does not need to be added to settings.INSTALLED_APPS anymore.
• RpcNamespace were added to provide a better organization of procedures. Each one can be registered in a previously defined RpcServer.
• It is now possible to register async procedures. Both sync (legacy) and async procedures are served by the default view (synchronous)
• For improved performances with async procedures, an async view has been added and can be used as a replacement to expose procedures. The async_view can serve both sync and async procedures.
• Error handling has been improved, allowing executing a callback function when an exception is caught and before an RPC error response is built.
• The authentication process has been improved. Multiple callbacks can be configured at server-level, namespace-level or directly on a specific remote procedure.
• It is now possible to configure different backends to deserialize XML-RPC and JSON-RPC requests and to serialize XML-RPC and JSON-RPC responses. Alternative backends may provide more features, configuration options, specific types support or better performances.

Breaking Changes

• Complete architecture redesign: The library now uses a server-based approach instead of entry points
• Removed the RPCEntryPoint class-based view in favor of the new function based views provided by RpcServer class
• Removed automatic procedure registration via MODERNRPC_METHODS_MODULES setting
• Removed HTML documentation generation through entry points
• Changed the way procedures access request context, now using the context_target parameter
• Some settings were removed:
  • MODERNRPC_METHODS_MODULES
  • MODERNRPC_LOG_EXCEPTIONS
  • MODERNRPC_DEFAULT_ENTRYPOINT_NAME
  • MODERNRPC_JSON_DECODER
  • MODERNRPC_JSON_ENCODER
  • MODERNRPC_XMLRPC_USE_BUILTIN_TYPES

... (truncated)

Changelog

Sourced from django-modern-rpc's changelog.

v2.1.0

Release date: 2026-06-05

Improvements

• A new JSON-RPC backend based on the third party library ujson has been added.
• It is now possible to call a procedure without the "params" argument in a multicall request.

Breaking Changes

• AuthenticationError now uses a dedicated error code (-32098) instead of the generic internal error code (-32603). Clients relying on the error code to detect authentication failures should update their checks accordingly.

Misc

• Dropped support for Django < 4.2
• Dropped support for Python < 3.10

v2.0.0

Release date: 2025-11-10

Improvements

• The new API, heavily inspired from tools like FastAPI or django-ninja, encapsulates the procedures registration in a dedicated RpcServer instance. This removes the need to lookup modules based on settings.MODERNRPC_METHODS_MODULES value, so modernrpc does not need to be added to settings.INSTALLED_APPS anymore.
• RpcNamespace was added to provide a better organization of procedures. Each one can be registered in a previously defined RpcServer.
• It is now possible to register async procedures. Both sync (legacy) and async procedures are served by the default view (synchronous).
• For improved performances with async procedures, an async view has been added and can be used as a replacement to expose procedures. The async_view can serve both sync and async procedures.
• Error handling has been improved, allowing execution of a callback function when an exception is caught and before an RPC error response is built.
• The authentication process has been improved. Multiple callbacks can be configured at server-level, namespace-level or directly on a specific remote procedure.
• It is now possible to configure different backends to deserialize XML-RPC and JSON-RPC requests and to serialize XML-RPC and JSON-RPC responses. Alternative backends may provide more features, configuration options, specific types support or better performances.

Breaking Changes

• Complete architecture redesign: The library now uses a server-based approach instead of entry points
• Removed the RPCEntryPoint class-based view in favor of the new function based views provided by RpcServer class
• Removed automatic procedure registration via MODERNRPC_METHODS_MODULES setting
• Removed HTML documentation generation through entry points
• Changed the way procedures access request context, now using the context_target parameter
• Some settings were removed:

... (truncated)

Commits

• fa3ef47 Bump 2.1.0
• 7b5eae9 [test] Added tests for allow_none arg in XML unmarshallers
• a118c50 [actions] Fixed dependency version for upload/download artifact
• 177af00 [test] Fixed ResourceWarning: unclosed <socket.socket> from XML-RPC calls
• 2fa0e4a [core] Removed a DeprecationWarning from docutils
• 3e7048b [test] Check exception raised when None value is disallowed in xmlrpc
• ae4a1f2 [core] Use functools.cached_property instead of Django one
• c049c4f [actions] Update third-party actions versions
• 82afb3c Fixed latest issues returned by ty
• bb31ea8 [docs] Multiple improvements
• Additional commits viewable in compare view