This repository was archived by the owner on Sep 30, 2024. It is now read-only.
fix(client): restore paths for extension bundles#63402
Merged
Merged
Conversation
mike-r-mclaughlin
left a comment
Contributor
There was a problem hiding this comment.
looks good. is there a way to confirm the integration tests are running? just trying to think of a way to make sure this doesn't happen again
eseliger
approved these changes
Jun 20, 2024
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
When moving to ESBuild, the filenames for extension bundles changed, which led to broken bitbucket plugins for example.
See discussion
Test plan
Inspected the relevant target to see the paths in their proper location.
Changelog