Skip to content

Remove pinned SDK versions for latest resolution#768

Open
THardy98 wants to merge 5 commits intomainfrom
feature/pull-latest-package-manager
Open

Remove pinned SDK versions for latest resolution#768
THardy98 wants to merge 5 commits intomainfrom
feature/pull-latest-package-manager

Conversation

@THardy98
Copy link
Contributor

@THardy98 THardy98 commented Mar 8, 2026

Summary

  • Remove pinned SDK versions from all language manifest files and delete lock files so local builds default to the latest SDK release via each package manager's native resolution
  • Update Python and Ruby Go harness code to explicitly handle empty version constraints
  • Switch CI from npm ci to npm install since lock file is no longer committed

Closes #761

Test plan

  • Verify go build ./... compiles cleanly
  • Run local builds for each language without --version flag and confirm latest SDK is resolved
  • Verify CI still works with explicit --version override

🤖 Generated with Claude Code

@THardy98 THardy98 force-pushed the feature/pull-latest-package-manager branch from 9330c86 to 884269c Compare March 9, 2026 13:58
THardy98 and others added 5 commits March 9, 2026 17:38
Remove version constraints from manifest files and delete lock files so
local builds default to the latest SDK version. CI is unaffected as it
already discovers and passes the latest version via the GitHub API.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove redundant rubocop disable directive in harness/ruby/runner.rb
- Suppress eslint import/no-named-as-default for ms import in TS feature

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Match the pattern used in sdkbuild/python.go — check features/ and
harness/python/ instead of '.' which scans into .venv/ and hits
incompatible stubs with the pinned mypy version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The pin to 0.961 (from 2022) can't parse positional-only parameter
syntax in newer google-stubs that ship with latest protobuf. Also
reverts the directory-targeting workaround which didn't help.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@THardy98 THardy98 force-pushed the feature/pull-latest-package-manager branch from af7ab20 to c94c5db Compare March 9, 2026 21:38
@THardy98 THardy98 marked this pull request as ready for review March 9, 2026 21:38
@THardy98 THardy98 requested review from a team as code owners March 9, 2026 21:38
Copy link
Member

@Sushisource Sushisource left a comment

Choose a reason for hiding this comment

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

Hmm... I get why we removed the lock files to allow this to work, but, ideally we want to be able to keep the various other deps locked still, since otherwise we're subject to random upgrade-related issues.

We could have the harness run the npm/uv update before executing?

@Sushisource
Copy link
Member

Some addtl. context to take into account: https://temporaltechnologies.slack.com/archives/C01FG4BRQVB/p1773257442027009

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Have features repo pull the package manager's latest SDK version

2 participants