@plutolang/pluto-infra@0.4.8

Patch Changes

• 6859583: fix(sdk): pulumi serialization issue with pluto-info package

  Deploying the pluto application on Kubernetes works locally, but fails in container environments where packages are fetched from the npm registry instead of being built locally. This failure is due to pulumi not serializing the imported package correctly. In the dev environment, serialization includes all imported package code, but in containers, it only generates a require statement, causing the application to fail.

  To resolve this, I adapted a serialization method that was previously implemented for Python, creating an adapter file for each resource. Then, wrapping functions from the business layer to the adapter, then to the base runtime function, in sequence. These files are then bundled according to dependency hierarchy into a directory, from which an image is built and deployed to Kubernetes.

@plutolang/cli@0.4.12

Patch Changes

• @plutolang/simulator-adapter@0.3.12

@plutolang/simulator-adapter@0.3.11

Patch Changes

• Updated dependencies [aa14b9c]
  • @plutolang/pluto-infra@0.4.7

@plutolang/pulumi-adapter@0.4.3

Patch Changes

• aa14b9c: feat(adapter,sdk): allow custom registry URL and platform for application deployment on K8s

@plutolang/pluto-infra@0.4.7

Patch Changes

• aa14b9c: feat(adapter,sdk): allow custom registry URL and platform for application deployment on K8s

@plutolang/cli@0.4.11

Patch Changes

• Updated dependencies [aa14b9c]
  • @plutolang/pulumi-adapter@0.4.3
  • @plutolang/simulator-adapter@0.3.11

@plutolang/pyright-deducer@0.1.7

Patch Changes

• 4d74eb6: fix(deducer): correct exportName setting for multiline export statements

  This commit addresses an issue where errors occur when setting the exportName for export statements that contain line breaks. The issue arises particularly when the export statement is a function call, lambda expression, or similar, and spans multiple lines.

  Previously, the strategy was to assign the last line of the statement to the exportName, which proved to be incorrect for multiline statements. This commit changes that approach to assign the entire statement to the exportName, if the statement spans multiple lines.

  Consider the following function call, where the second argument is the statement we want to export:

  router.all("/*", lambda *args, **kwargs: Mangum(return_fastapi_app(),
                                                  api_gateway_base_path="/dev")(*args, **kwargs), raw=True)

  Before this fix, the assignment would look like this:

  lambda *args, **kwargs: Mangum(return_fastapi_app(),
  exportName                                                api_gateway_base_path="/dev")(*args, **kwargs)

  After this fix, the assignment is as follows:

  exportName = lambda *args, **kwargs: Mangum(return_fastapi_app(),
                                                  api_gateway_base_path="/dev")(*args, **kwargs)

@plutolang/cli@0.4.10

Patch Changes

• Updated dependencies [4d74eb6]
  • @plutolang/pyright-deducer@0.1.7

@plutolang/simulator-adapter@0.3.10

Patch Changes

• Updated dependencies [bfded23]
  • @plutolang/pluto-infra@0.4.6

@plutolang/pyright-deducer@0.1.6

Patch Changes

• bfded23: feat(deducer): expand support for python runtimes

  Recognizing that the Python runtime on a developer's device may not always be 'python3.10', we have extended our support to include a broader range of Python runtimes. The updated requirements now stipulate that the Python runtime should be 'python3.8' or higher, but not exceeding 'python3.12'.