Releases: pluto-lang/pluto
@plutolang/[email protected]
Patch Changes
-
3db055d: feat(deducer): configure local arch for pluto run on Mac
Avoid unnecessary use of Docker for x86 pypi package downloads when executing pluto run on Mac. Previously, target architecture was set to x86 for all environments, leading to Docker usage on Mac. This change sets the target architecture to the local one during pluto run execution.
@plutolang/[email protected]
Patch Changes
-
3db055d: feat(deducer): configure local arch for pluto run on Mac
Avoid unnecessary use of Docker for x86 pypi package downloads when executing pluto run on Mac. Previously, target architecture was set to x86 for all environments, leading to Docker usage on Mac. This change sets the target architecture to the local one during pluto run execution.
-
Updated dependencies [3db055d]
- @plutolang/[email protected]
@plutolang/[email protected]
Patch Changes
- abc80a8: feat(simulator): support custom address configuration
- Updated dependencies [03f1602]
- Updated dependencies [ee30573]
- @plutolang/[email protected]
- @plutolang/[email protected]
@plutolang/[email protected]
Patch Changes
-
03f1602: feat(sdk): add support for configuring host and port for website resource
This change introduces the ability to specify custom host and port settings for website resources, enhancing flexibility during local development.
-
ee30573: feat(sdk): add support for configuring host and port for router resource
This change introduces the ability to specify custom host and port settings for router resources, enhancing flexibility during local development.
@plutolang/[email protected]
Patch Changes
-
03f1602: feat(sdk): add support for configuring host and port for website resource
This change introduces the ability to specify custom host and port settings for website resources, enhancing flexibility during local development.
-
ee30573: feat(sdk): add support for configuring host and port for router resource
This change introduces the ability to specify custom host and port settings for router resources, enhancing flexibility during local development.
-
Updated dependencies [03f1602]
-
Updated dependencies [ee30573]
- @plutolang/[email protected]
@plutolang/[email protected]
Patch Changes
- abc80a8: feat(simulator): support custom address configuration
- Updated dependencies [abc80a8]
- @plutolang/[email protected]
- @plutolang/[email protected]
@plutolang/[email protected]
Patch Changes
-
75e5a89: feat(simulator): support sub-package resource definitions
Allow resource types to be defined within sub-packages, extending the previous limitation of only allowing definitions in the root package. This enhancement enables the simulator to process resources that are defined in sub-packages.
@plutolang/[email protected]
Patch Changes
- Updated dependencies [75e5a89]
- @plutolang/[email protected]
@plutolang/[email protected]
Patch Changes
-
f6b3536: fix(deducer): correct package directory resolution and METADATA parsing
This commit addresses two separate issues identified in the deducer:
- The deducer incorrectly searched for distribution information within the stub type directory, which lacks the required dist info. The resolution has been updated to check for the presence of
nonStubImportResult
within theImportResult
. If present, it is now utilized to determine the correct package directory. - The parsing of the
dist-info/METADATA
file was flawed due to the possibility of encountering multipleName
lines. The parser has been adjusted to only consider lines that begin withName:
and are not preceded by any spaces.
- The deducer incorrectly searched for distribution information within the stub type directory, which lacks the required dist info. The resolution has been updated to check for the presence of
-
5e7702e: fix(deducer): avoid retrieving declarations for non-infrastructure call nodes
Previously, the deducer attempted to retrieve all call node declarations and match them against custom infrastructure functions. This method was flawed as functions with multiple declarations caused the deducer to fail. To address this, we now first verify that a call node pertains to a custom infrastructure function by comparing function names. Only then do we fetch the call node's declaration, effectively bypassing the collection of extraneous call node declarations.
@plutolang/[email protected]
Patch Changes
- Updated dependencies [f6b3536]
- Updated dependencies [5e7702e]
- @plutolang/[email protected]