chore: version packages #39
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@resourcexjs/registry@2.4.0
Minor Changes
8669eb7: feat: introduce BundledType for sandbox-compatible execution
Breaking changes:
ResourceType.resolverclosure replaced withBundledType.codestringtextType,jsonType,binaryTypeare now BundledType (pre-bundled)Registry.supportType()now accepts BundledType instead of ResourceTypeTypeHandlerChain.register()now accepts BundledTypeNew exports:
BundledTypeinterface - pre-bundled type with code stringSandboxType- "none" | "isolated" | "container"bundleResourceType()- bundle custom types from source filesMigration:
7a46fbf: refactor: remove serializer from ResourceType, unify storage format
Breaking Changes:
ResourceSerializerinterface from@resourcexjs/typeserializerfield fromResourceTypeinterfaceserialize()anddeserialize()methods fromTypeHandlerChainMigration:
If you have custom resource types with serializers, remove the
serializerfield:Internal Changes:
archive.buffer()directly instead of type-specific serializationadd()time viatypeHandler.canHandle()f9e6bdf: feat: implement sandbox execution architecture
Patch Changes
resourcexjs@2.4.0
Minor Changes
8669eb7: feat: introduce BundledType for sandbox-compatible execution
Breaking changes:
ResourceType.resolverclosure replaced withBundledType.codestringtextType,jsonType,binaryTypeare now BundledType (pre-bundled)Registry.supportType()now accepts BundledType instead of ResourceTypeTypeHandlerChain.register()now accepts BundledTypeNew exports:
BundledTypeinterface - pre-bundled type with code stringSandboxType- "none" | "isolated" | "container"bundleResourceType()- bundle custom types from source filesMigration:
f9e6bdf: feat: implement sandbox execution architecture
Patch Changes
@resourcexjs/type@2.4.0
Minor Changes
8669eb7: feat: introduce BundledType for sandbox-compatible execution
Breaking changes:
ResourceType.resolverclosure replaced withBundledType.codestringtextType,jsonType,binaryTypeare now BundledType (pre-bundled)Registry.supportType()now accepts BundledType instead of ResourceTypeTypeHandlerChain.register()now accepts BundledTypeNew exports:
BundledTypeinterface - pre-bundled type with code stringSandboxType- "none" | "isolated" | "container"bundleResourceType()- bundle custom types from source filesMigration:
7a46fbf: refactor: remove serializer from ResourceType, unify storage format
Breaking Changes:
ResourceSerializerinterface from@resourcexjs/typeserializerfield fromResourceTypeinterfaceserialize()anddeserialize()methods fromTypeHandlerChainMigration:
If you have custom resource types with serializers, remove the
serializerfield:Internal Changes:
archive.buffer()directly instead of type-specific serializationadd()time viatypeHandler.canHandle()f9e6bdf: feat: implement sandbox execution architecture
Patch Changes
@resourcexjs/loader@2.4.0
Patch Changes
@resourcexjs/arp@2.4.0
@resourcexjs/core@2.4.0