CONN-1273: replace Speakeasy generate/release workflows with thin stubs - #673
Open
mcollinscodat wants to merge 11 commits into
Open
CONN-1273: replace Speakeasy generate/release workflows with thin stubs#673mcollinscodat wants to merge 11 commits into
mcollinscodat wants to merge 11 commits into
Conversation
…flows with thin stubs pointing at the central pipeline - bank_feeds_generate.yaml - generation moved to Codat SDK Codegen; stub warns and exits 0 - bank_feeds_release.yaml - queues the central Azure DevOps npm publish pipeline - lending_generate.yaml - generation moved to Codat SDK Codegen; stub warns and exits 0 - lending_release.yaml - queues the central Azure DevOps npm publish pipeline - platform_generate.yaml - generation moved to Codat SDK Codegen; stub warns and exits 0 - platform_release.yaml - queues the central Azure DevOps npm publish pipeline - sync_for_expenses_generate.yaml - generation moved to Codat SDK Codegen; stub warns and exits 0 - sync_for_expenses_release.yaml - queues the central Azure DevOps npm publish pipeline - sync_for_payables_generate.yaml - generation moved to Codat SDK Codegen; stub warns and exits 0 - sync_for_payables_release.yaml - queues the central Azure DevOps npm publish pipeline
…ish pipeline, and the pipeline itself lands in this repo .azuredevops/npm-publish.yml - new: builds, checks and publishes the released package to npm, triggered by the push to <product>/RELEASES.md; written by sdk-codegen (cutover/npm_publish_pipeline.yml), do not edit by hand .github/workflows/bank_feeds_release.yaml - stub no longer queues Azure DevOps over REST, it just records where publishing went; no token, no pipeline url, no concurrency group .github/workflows/lending_release.yaml - same .github/workflows/platform_release.yaml - same .github/workflows/sync_for_expenses_release.yaml - same .github/workflows/sync_for_payables_release.yaml - same
…ts comments were reworded .azuredevops/npm-publish.yml - re-emitted from cutover/npm_publish_pipeline.yml in sdk-codegen: clearer header comments and the two source paths now read from $(Build.SourcesDirectory); no change to what the pipeline does
… tidied .azuredevops/npm-publish.yml - the header no longer says "this repo", which flipped meaning depending on which copy you read; it names both repos and carries the written-by line the stubs have .github/workflows - all ten stubs: the written-by line names just the emitter file, not its path
mcollinscodat
marked this pull request as ready for review
August 11, 2026 11:12
…a release gets tagged again - .azuredevops/npm-publish.yml - re-emitted from sdk-codegen main: brings back the release-facts step, the OAS variable group, the GitHub App token mint, and the tag and GitHub release steps that were added to the pipeline centrally after this branch was last delivered
…ine so the build skips lint tooling the feed lacks - .azuredevops/npm-publish.yml - build step installs prod deps + the pinned TypeScript compiler and skips the eslint/typescript-eslint toolchain (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
…ine so the compiler install omits dev deps - .azuredevops/npm-publish.yml - the typescript install now passes --omit=dev so it no longer pulls the eslint/typescript-eslint tree (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
…ine to install the compiler in isolation - .azuredevops/npm-publish.yml - install TypeScript in a directory with no package.json and build with it on PATH, so npm never resolves the eslint/typescript-eslint dev tree (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
…ine so the tarball tripwire matches the SDK layout - .azuredevops/npm-publish.yml - tripwire checks built .js at the package root and the declared entry point, not a dist/ dir these SDKs never produce (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
…ine with the SIGPIPE-safe tarball tripwire - .azuredevops/npm-publish.yml - tripwire lists the tarball once and matches with here-strings so grep/head no longer SIGPIPEs tar under pipefail (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
…ine to pin the consumer's TypeScript - .azuredevops/npm-publish.yml - scratch consumer pins typescript at the SDK's version so it doesn't pull native TS 7 (delivered verbatim from sdk-codegen npm_publish_pipeline.yml)
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
1 participant
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.
Replaces the Speakeasy generate and release workflows for bank-feeds, lending, platform, sync-for-expenses and sync-for-payables with thin stubs pointing at Codat's central SDK codegen pipeline, and adds the Azure DevOps pipeline that publishes these packages to npm. Workflow filenames and names are unchanged so existing triggers keep matching. Workflows for the other products are untouched.
<product>/RELEASES.mdpushes to main (plus manual dispatch), but publishing runs centrally now, so the stub only records where it went. The Azure DevOps pipeline watches that same push itself, so the stub has nothing to queue and needs no credential. No packaging check has been dropped; they all run centrally..azuredevops/npm-publish.yml: the pipeline that builds, checks and publishes the released package. It lives here because an Azure Pipelines CI trigger only fires for the repo its YAML sits in. Generated bycutover/emit_workflow_stubs.py --lang tsfromcutover/npm_publish_pipeline.ymlin sdk-codegen, so it stays a delivery rather than a hand-maintained copy.No secrets or variables need setting on this repo. Merge order is codat-internal/sdk-codegen#362 (the pipeline) then #360 (the emitter that produced this output), so the tool behind these files is on main before this lands.