Deta Space engine version constraints and language syntax compatibility

Deta Space applications are configured via a Spacefile that defines the runtime engine, such as Python or Node.js families. Because the platform pins specific language versions to these engines, there is a potential mismatch between local development environments and the hosted runtime provided by Deta.

When a developer utilizes syntax from a newer language release—such as specific Python type hinting or modern Node.js features—that is not yet supported by the pinned Space engine version, the Micro may fail during execution. This is particularly relevant when the app relies on external libraries that require a minimum version of the underlying runtime.

How can developers determine the exact range of supported language versions for each engine in Deta Space before deployment, and is there a mechanism to pin a specific minor version within the Spacefile to prevent breaking changes during updates?