Pin tsp-client version in pipeline
Open
needs-triage
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Seems that .net pipelines currently install tsp-client with the `@latest` tag/without specifying a specific package version, which can cause issues for the pipeline if there's a problem in the latest tsp-client version.
It would be best to pin tsp-client to a specific version and test new versions before updating the entire pipeline.
cc @mikeharder @raych1 @m-nash
Contributor guide
Research direction
Locate the .NET pipeline steps that install tsp-client and identify where the @latest tag is specified. Pin the package to a specific version, then verify the pipeline can test newer tsp-client versions before an update is adopted.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100