Repository navigation
Wire typescript generation - #13
Merged
colinjlacy merged 2 commits intoOct 23, 2026
Merged
Conversation
Add TypeScript targets for common-integrations and env-configuration to the package catalog, named @runtimeconditions/<package key>, and a generate-typescript.py script that normalizes each model with rc, runs the TypeScript emitter, verifies the package, and adds the model, the root extension, and a file manifest like the Go and Python packages have. The generation workflow now runs it and commits bindings/<key>/typescript to main. rc selects only the languages it emits itself when no target is given, so a catalog language with its own script no longer breaks rc bindings check and update. Signed-off-by: itvi-1234 <rjsumit71@gmail.com>
Replace the placeholder with a workflow that builds the committed TypeScript packages in dependency order, checks them with npm pack, and publishes the ones that are not on npm yet. The job requests an OIDC token (id-token: write), so npm authenticates the workflow itself and no npm token is stored. It defaults to a dry run. Signed-off-by: itvi-1234 <rjsumit71@gmail.com>
colinjlacy
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
1. Generate TypeScript bindings in CI
packages.yamlgets atypescriptentry forcommon-integrationsandenv-configuration. The names are@runtimeconditions/common-integrationsand@runtimeconditions/env-configuration.ci/generate-typescript.py. For each package it makes the model withrc, runs the TypeScript emitter, checks the result, and adds the model, the extension and a file manifest.binding-toolsaction now run it, and commitbindings/<key>/typescripttomain, the same way as Go and Python.2. Publish to npm with trusted publishing
binding-publish-npm.ymlis no longer a placeholder.id-token: write, so npm trusts the workflow itself. No npm token is stored anywhere.main, and only when someone starts it.How I tested it
tsc, and a second run gave the same result.