Skip to content
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

Changes made to non-dune pinned packages are not visible until dune clean is run #10232

Closed
gridbugs opened this issue Mar 8, 2024 · 0 comments · Fixed by #10512
Closed

Changes made to non-dune pinned packages are not visible until dune clean is run #10232

gridbugs opened this issue Mar 8, 2024 · 0 comments · Fixed by #10512

Comments

@gridbugs
Copy link
Collaborator

gridbugs commented Mar 8, 2024

After dune attempts to build a non-dune pinned package, changes to the pinned package are not picked up by dune until dune clean is run, even if the attempt to build the pinned package failed.

Changes to the pinned package should be picked up immediately regardless of the state of the current project and trigger rebuilds as necessary.

Repro test added in: #10233

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

Successfully merging a pull request may close this issue.

1 participant