Version Packages

[kriskowal]

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 master, this PR will be updated.

Releases

@endo/compartment-mapper@2.3.0

Minor Changes

• #2422 fe6be07 Thanks @kriskowal! - Add support for host module exits in bundled compartments.

  ses exports a new StrictModuleDescriptor type that consists only of the
  NamespaceModuleDescriptor and SourceModuleDescriptor shapes mutually
  supported by SES and XS.

  compartment-mapper lets arbitrary module descriptors pass through
  importHook when no policy is in effect for that edge (the
  policy-enforcement runtime was previously limited to virtual module sources).
  It also implicitly treats any module specifier with a URL-scheme prefix
  (like node:fs) as an exit module when bundling, removing the need for an
  additional bundler flag in the common case.

  import-bundle threads the importHook option through to the underlying
  compartment so that bundled applications can route exits to host-provided
  implementations at import time.
  Host-provided modules must be hardened and pure to avoid being a
  side-channel or man-in-the-middle attack surface between guests.

Patch Changes

• #3186 d5e2498 Thanks @boneskull! - Fixes poorly-defined support for asynchronous parsers.

• Updated dependencies [889be5e, fe6be07]:

  • ses@2.2.0

@endo/eslint-plugin@2.6.0

Minor Changes

• #3263 c423ed3 Thanks @kriskowal! - The internal preset now enforces unicorn/numeric-separators-style with
  default groupings: decimal numbers of five or more digits must use underscore
  separators every three digits, and hexadecimal, binary, and octal literals must
  use the rule's conventional group lengths.
  Consumers of plugin:@endo/internal will see lint errors on numeric literals
  that violate the rule; eslint --fix rewrites them automatically.
  Sites extending the preset must add eslint-plugin-unicorn to their devDeps.

• #3277 da632a2 Thanks @kriskowal! - The @endo/harden-exports rule now skips named exports whose initializer is
  a Pattern maker call of the form M.something(...).
  Pattern makers return values that are already hardened, so a follow-up
  harden(name) after their export is redundant noise.

  A new companion rule, @endo/no-harden-pattern-maker, surfaces existing
  sites where code over-hardens a Pattern maker result.
  The rule fires on both harden(M.string()) and the indirect form
  const x = M.string(); harden(x);, and is included in the recommended
  configuration as a warning so existing code doesn't break loudly while
  the redundant calls are cleaned up.

Patch Changes

• #3292 62d1b0a Thanks @turadg! - Declare @typescript-eslint/* and typescript-eslint as caret ranges
  (^8.39.1) rather than exact pins, so consumers can dedupe them against
  their own typescript-eslint versions instead of being forced onto a
  single release. Also drop the redundant parserOptions.project from the
  internal config: typescript-eslint 8.60 errors when project is set
  alongside projectService, which now supplies the type-aware program.

@endo/import-bundle@1.7.0

Minor Changes

• #2422 fe6be07 Thanks @kriskowal! - Add support for host module exits in bundled compartments.

  ses exports a new StrictModuleDescriptor type that consists only of the
  NamespaceModuleDescriptor and SourceModuleDescriptor shapes mutually
  supported by SES and XS.

  compartment-mapper lets arbitrary module descriptors pass through
  importHook when no policy is in effect for that edge (the
  policy-enforcement runtime was previously limited to virtual module sources).
  It also implicitly treats any module specifier with a URL-scheme prefix
  (like node:fs) as an exit module when bundling, removing the need for an
  additional bundler flag in the common case.

  import-bundle threads the importHook option through to the underlying
  compartment so that bundled applications can route exits to host-provided
  implementations at import time.
  Host-provided modules must be hardened and pure to avoid being a
  side-channel or man-in-the-middle attack surface between guests.

Patch Changes

• Updated dependencies [d5e2498, 889be5e, fe6be07]:
  • @endo/compartment-mapper@2.3.0
  • ses@2.2.0

ses@2.2.0

Minor Changes

• #3285 889be5e Thanks @erights! - Permit both initial powerful Temporal and safe shared Temporal

• #2422 fe6be07 Thanks @kriskowal! - Add support for host module exits in bundled compartments.

  ses exports a new StrictModuleDescriptor type that consists only of the
  NamespaceModuleDescriptor and SourceModuleDescriptor shapes mutually
  supported by SES and XS.

  compartment-mapper lets arbitrary module descriptors pass through
  importHook when no policy is in effect for that edge (the
  policy-enforcement runtime was previously limited to virtual module sources).
  It also implicitly treats any module specifier with a URL-scheme prefix
  (like node:fs) as an exit module when bundling, removing the need for an
  additional bundler flag in the common case.

  import-bundle threads the importHook option through to the underlying
  compartment so that bundled applications can route exits to host-provided
  implementations at import time.
  Host-provided modules must be hardened and pure to avoid being a
  side-channel or man-in-the-middle attack surface between guests.

@endo/bundle-source@4.3.2

Patch Changes

• #3186 d5e2498 Thanks @boneskull! - Fixes poorly-defined support for asynchronous parsers.

• Updated dependencies [d5e2498, fe6be07]:

  • @endo/compartment-mapper@2.3.0

@endo/pass-style@1.8.1

Patch Changes

• #3292 dd0face Thanks @turadg! - Update the tools/arb-passable arbitrary for the fast-check 4 API:
  fullUnicodeString() was removed, so it now uses the documented
  equivalent string({ unit: 'binary' }). Consumers using this arbitrary
  should depend on fast-check 4.

  Also pass noNullPrototype: true to the record/dictionary arbitraries:
  fast-check 4 generates {__proto__:null} objects by default, which are
  not valid copyRecords (they must inherit from Object.prototype), so
  without this the arbitrary produced invalid passables.

@endo/ses-ava@1.4.2

Patch Changes

• #3292 1c34f07 Thanks @turadg! - Widen the declared ava dependency range to ^6 || ^7 || ^8 so
  consumers can stay on ava 6 or 7 rather than being forced onto ava 8.
  It remains a direct dependency (not a peer) so the ses-ava bin
  materializes correctly under the pnpm linker.
• Updated dependencies [889be5e, fe6be07]:
  • ses@2.2.0