Skip to content

Latest commit

 

History

History
259 lines (189 loc) · 9.22 KB

CONTRIBUTING.md

File metadata and controls

259 lines (189 loc) · 9.22 KB
Raw

How to Contribute

Table of Contents

The TypeScript SDK (as well as the rest of the Temporal codebase) is open sourced under the MIT license.

We welcome contributions from the community. To contribute, please start by opening an issue and discussing the proposed change. Once a change has been agreed upon, development may start and be submitted via a pull request.

Maintenance

The current maintainers are:

If you'd like to join us, email Roey. We'd be happy to have help with any of these things:

  • Triaging issues
  • Reviewing PRs
  • Submitting PRs to close issues

Getting started

Contributor License Agreement (CLA)

Contributors must agree to the CLA before their PR can be merged. You only have to do this once. Follow this link and sign in with your GitHub account.

SDK Structure

See sdk-structure.md

Environment setup

  • Install Node 16 and Temporal Server
  • Install the Rust toolchain
  • Install Protocal Buffers
  • Clone the sdk-typescript repo: 
    git clone https://github.com/temporalio/sdk-typescript.git
cd sdk-typescript
  • Initialize the Core SDK submodule: 
    git submodule update --init --recursive

    If you get a The authenticity of host 'github.com (192.30.252.123)' can't be established. error, run ssh-keyscan github.com >> ~/.ssh/known_hosts and retry.

  • Install the dependencies: 
    npm ci
    This may take a few minutes, as it involves downloading and compiling Rust dependencies.
  • You should now be able to build: 
    npm run build

If building fails, resetting your environment may help:

npx lerna clean -y && npm ci

If npm ci fails in @temporalio/core-bridge on the command node ./scripts/build.js, you may need to do rustup update.

To update to the latest version of the Core SDK, run git submodule update followed by npm run build to recompile.

For cross compilation on MacOS follow these instructions (only required for publishing packages).

Development

After your environment is set up, you can run these commands:

  • npm run build compiles protobuf definitions, Rust bridge, C++ isolate extension, and Typescript.
  • npm run rebuild deletes all generated files in the project and reruns build.
  • npm run build.watch watches filesystem for changes and incrementally compiles Typescript on change.
  • npm run test runs the test suite.
  • npm run test.watch runs the test suite on each change to Typescript files.
  • npm run format formats code with prettier.
  • npm run lint verifies code style with prettier and ES lint.
  • npm run commitlint validates commit messages.

Testing

Testing local changes to core

Create a .cargo/config.toml file and override the path to sdk-core and/or sdk-core-protos as described here

Integration tests

In order to run integration tests:

  1. Run the temporal server using docker-compose.
  2. Export RUN_INTEGRATION_TESTS=true

test-npm-init

To replicate the test-npm-init CI test locally, you can start with the below steps:

If you've run npx @temporalio/create before, you may need to delete the version of the package that's stored in ~/.npm/_npx/.

rm -rf /tmp/registry
npm ci
npm run rebuild
node scripts/publish-to-verdaccio.js --registry-dir /tmp/registry
node scripts/init-from-verdaccio.js --registry-dir /tmp/registry --sample hello-world
cd /tmp/registry/example
npm run build
node ~/path-to/sdk-typescript/scripts/test-example.js --work-dir /tmp/registry/example

Style Guide

<type>(optional scope): <description>

chore(samples): upgrade commander module

The scope options are listed in commitlint.config.js.

Publishing

First, follow the instructions in docs/building.md.

cargo install git-cliff
# git-cliff --tag <new version> <current version>..HEAD | pbcopy
git-cliff --tag 1.0.1 v1.0.0..HEAD | pbcopy
  • Paste into CHANGELOG.md
  • Clean up formatting
  • Add any important missing details
  • Replace PR numbers with links:
#(\d{3})
[#$1](https://github.com/temporalio/sdk-typescript/pull/$1)
  • If PRs came from external contributors, thank them & link their github handles: ([#484](link), thanks to [@user](https://github.com/user) 🙏)
  • Open PR with CHANGELOG change
  • If using a custom features branch for PR integration tests, make sure the branch is fully up-to-date with features main before merging the CHANGELOG PR
  • Merge PR
  • Checkout latest main

We're working on automating the rest of the process:

  • Log in to npm as temporal-sdk-team (npm whoami and npm login)
  • Download the 5 packages-* artifacts from the PR's GitHub Action
  • Publish:
#!/bin/bash
set -euo pipefail

git clean -fdx
npm ci
npm run build

mkdir -p packages/core-bridge/releases

# in the next command, replace ~/gh/release-sdk-typescript with your dir
for f in ~/Downloads/packages-*.zip; do mkdir "$HOME/Downloads/$(basename -s .zip $f)"; (cd "$HOME/Downloads/$(basename -s .zip $f)" && unzip $f && tar -xvzf @temporalio/core-bridge/core-bridge-*.tgz package/releases/ && cp -r package/releases/* ~/gh/release-sdk-typescript/packages/core-bridge/releases/); done

# we should now have all 5 build targets
ls packages/core-bridge/releases/

npx lerna version patch --force-publish='*' # or major|minor|etc, or leave out to be prompted. either way, you get a confirmation dialog.

git checkout -B fix-deps
node scripts/prepublish.mjs
git commit -am 'Fix dependencies'
npx lerna publish from-package # add `--dist-tag next` for pre-release versions
git checkout -

Finally:

npm deprecate temporalio@^1.0.0 "Instead of installing temporalio, we recommend directly installing our packages: npm remove temporalio; npm install @temporalio/client @temporalio/worker @temporalio/workflow @temporalio/activity"

  • Cleanup after publishing:

    rm -rf $HOME/Downloads/packages-*
rm -rf packages/core-bridge/releases/*

  • If using a custom features branch for PR integration tests, merge that branch into features main and update the SDK workflow definition to trigger features main

  • If any APIs have changed, open a PR to update samples-typescript. Once merged, update the next branch:

    git checkout next
git rebase origin/main
git push

  • While our tests should capture most things, if you want to verify the release works in the samples, do:

    cd /path/to/samples-typescript
lerna exec -- npm update
npm run build
npm test

Updating published packages

npm commands we may need to use:

If we publish a version like 1.1.0-rc.1 with tag next, we untag it after 1.1.0 is released:

npm dist-tag rm @temporalio/client next
npm dist-tag rm @temporalio/worker next
npm dist-tag rm @temporalio/workflow next
npm dist-tag rm @temporalio/activity next
npm dist-tag rm @temporalio/testing next
npm dist-tag rm @temporalio/common next
npm dist-tag rm @temporalio/proto next
npm dist-tag rm @temporalio/interceptors-opentelemetry next
npm dist-tag rm @temporalio/common/lib/internal-workflow next
npm dist-tag rm @temporalio/common/lib/internal-non-workflow next
npm dist-tag rm @temporalio/create next
npm dist-tag rm temporalio next