Fix TypeScript protobuf resolution

[stephanos]

Bump github.com/temporalio/features and TS SDK.

Alternatives considered:

• SDK 1.23 without the direct, pinned dependency: fails with "type must be a Type".
• SDK 1.22: fails because features overrides protobufjs to 8.x, while SDK 1.22 was built around the older protobuf stack.

[stephanos]

ie latest main

[stephanos]

The direct dependency is necessary because generated json-module.js performs require("protobufjs/light"). With pnpm, a transitive SDK dependency is not reliably visible there. Without a direct declaration, Node either cannot resolve it or finds the worker fixture’s protobufjs 7.x copy, producing incompatible runtime type identities.

[mjameswh]

@stephanos You are missing dependencies in "workers/typescript/package.json". Should be something like this:

  "dependencies": {
    ...
    "protobufjs": "^8.7.1",
    "protobufjs-cli": "^2.6.1",
    ...
  },

[mjameswh]

Makes sense.

[mjameswh]

This change is unexpected (i.e. you should not need that), and quite surprising (i.e. even assuming you need it, it should not point to a package.json file).

[stephanos]

Yes, it's odd eh?

I'll leave this claim from my agent here for posterity:

Without the app.ts alias, source-SDK builds can bundle two physical protobufjs 8.8.0 copies:

• Generated kitchen-sink protobuf types use the copy under prepared/node_modules.
• The SDK payload converter uses the copy resolved through @temporalio/common.

Even though both are version 8.8.0, their Type constructors have different identities. The SDK’s instanceof check then throws:

TypeError: type must be a Type

Workflow activations repeatedly fail, so the five-noop smoke test appears stuck indefinitely. Released SDK layouts may pass due to package-manager hoisting, but the source-build CI layout
does not reliably deduplicate them. The build.go entry installs the dependency; the app.ts hook enforces one physical copy in the bundle.