Skip to content

Conversation

justin39
Copy link
Contributor

Closes #255218

I opened that issue and it hasn't received its requisite 20 community upvotes, but it seems like a lightweight change. This is intended to avoid scenarios where code serve-web is unusable due to problems with the latest release client.

@justin39
Copy link
Contributor Author

@microsoft-github-policy-service agree company="Two Sigma"

@connor4312
Copy link
Member

This will still auto update to the latest commit after a period of time

@justin39
Copy link
Contributor Author

justin39 commented Jul 14, 2025

This will still auto update to the latest commit after a period of time

Good point, running the update checker is rather pointless if a commit SHA was passed in. I think this would've short-circuited to the commit SHA if passed, but better off not spawning the checker anyways - let me know if you had a different issue in mind that I've missed :)

@connor4312 connor4312 enabled auto-merge (squash) July 14, 2025 04:55
@connor4312
Copy link
Member

thanks!

@vs-code-engineering vs-code-engineering bot added this to the July 2025 milestone Jul 14, 2025
@connor4312 connor4312 merged commit b4d1fec into microsoft:main Jul 14, 2025
17 checks passed
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Aug 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support pinning client version when running via serve-web
4 participants