Skip to content

[CP] Pub: Fix to using path dependencies in git dependencies on windows #56116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sigurdm opened this issue Jul 1, 2024 · 2 comments
Closed
Assignees
Labels
cherry-pick-review Issue that need cherry pick triage to approve

Comments

@sigurdm
Copy link
Contributor

sigurdm commented Jul 1, 2024

Commit(s) to merge

https://dart-review.googlesource.com/c/sdk/+/373861 (rolling dart-lang/pub#4315)

Target

beta

Prepared changelist for beta/stable

https://dart-review.googlesource.com/c/sdk/+/373861

Issue Description

On windows the path would be written with a \ instead of / the pubspec lock, making it incompatible with the mac/linux pubspec.lock

What is the fix

Always use '/' in pubspec.lock for path-dependencies in git-dependencies.

Why cherry-pick

Windows users using the path-dependencies from git-dependencies feature are impacted, and will get an inconsistent pubspec.lock.

Risk

Low

Issue link(s)

dart-lang/pub#4314

Extra Info

We could consider also picking this to stable, but given that this was only discovered late, it might not be a broadly used feature, and we can get away with a beta CP.

@sigurdm sigurdm added the cherry-pick-review Issue that need cherry pick triage to approve label Jul 1, 2024
@jonasfj
Copy link
Member

jonasfj commented Jul 1, 2024

Support for relative path-dependencies from git-dependencies was introduced in Dart 3.4, this bug has existed since.

I don't think the feature has been widely promoted.

But it would be nice to get the fix into 3.5.

@itsjustkevin
Copy link
Contributor

itsjustkevin commented Jul 1, 2024

@sigurdm and @jonasfj we have not cut the final beta, if this change has already landed on main, it will be included in the next beta, ensuring that it is available for the 3.5 release. I am going to close this issue, please reopen if I understood incorrectly.

@itsjustkevin itsjustkevin added the cherry-pick-approved Label for approved cherrypick request label Jul 1, 2024
@itsjustkevin itsjustkevin removed the cherry-pick-approved Label for approved cherrypick request label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-review Issue that need cherry pick triage to approve
Projects
None yet
Development

No branches or pull requests

6 participants