Skip to content

chore: test new model generation in ci#7689

Merged
smilkuri merged 6 commits intomainfrom
test-newmodel-gen
Feb 3, 2026
Merged

chore: test new model generation in ci#7689
smilkuri merged 6 commits intomainfrom
test-newmodel-gen

Conversation

@smilkuri
Copy link
Copy Markdown
Contributor

@smilkuri smilkuri commented Jan 28, 2026

Issue

Internal JS-6480

Description

Adds new-client-test-codegen test model with Weather service and test the generation of client in pr-build workflow.

Testing

CI

Checklist

  • [n/a] If the PR is a feature, add integration tests (*.integ.spec.ts).
  • [n/a] If you wrote E2E tests, are they resilient to concurrent I/O?
  • [n/a] If adding new public functions, did you add the @public tag and enable doc generation on the package?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@smilkuri smilkuri force-pushed the test-newmodel-gen branch 5 times, most recently from 56bab77 to 0d08d14 Compare January 29, 2026 16:47
@smilkuri smilkuri marked this pull request as ready for review January 29, 2026 17:11
@smilkuri smilkuri requested a review from a team as a code owner January 29, 2026 17:11
Comment thread codegen/new-client-test-codegen/build.gradle.kts
Comment thread .github/workflows/codegen-ci.yml Outdated
run: |
cd codegen/new-client-test-codegen/build/smithyprojections/new-client-test-codegen/source/typescript-client-codegen
node ../../../../../../../scripts/runtime-dependency-version-check/runtime-dep-version-check.js
node ../../../../../../../scripts/runtime-dependency-version-check/check-dependencies.js
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why CD in if you're going to execute things outside the folder?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these the only validations run on generated clients?

this should be generated to the clients folder, a local commit made (for commit hooks), and then running integration tests (no e2e)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just realised the validation scripts use dirname to find the repo root, not process.cwd(). So cd isn't required. But, this script only scan packages, packages-internal, and private folders, so they won't validate the generated client in codegen/.../build/ anyway. Per the other comment, will generate this to clients/ folder and let the commit hooks run all validations instead.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generate into the /private folder

@smilkuri smilkuri force-pushed the test-newmodel-gen branch 2 times, most recently from 260dcd1 to 966e7eb Compare January 29, 2026 19:55
@smilkuri smilkuri marked this pull request as draft January 29, 2026 20:01
@smilkuri smilkuri marked this pull request as ready for review January 30, 2026 16:39
@smilkuri smilkuri merged commit c449f59 into main Feb 3, 2026
8 checks passed
@smilkuri smilkuri deleted the test-newmodel-gen branch February 3, 2026 18:54
@github-actions
Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Feb 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants