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

fix run_exports not applying to build-time requirements at top level #2613

Conversation

msarahan
Copy link
Contributor

@msarahan msarahan commented Jan 2, 2018

fixes #2607
fixes #2609

@msarahan msarahan force-pushed the fix_run_exports_not_applying_in_build_time_reqs branch from a07a78a to 30d5f18 Compare January 2, 2018 21:00
@msarahan msarahan force-pushed the fix_run_exports_not_applying_in_build_time_reqs branch from 30d5f18 to c9621b7 Compare January 2, 2018 21:28
@msarahan msarahan force-pushed the fix_run_exports_not_applying_in_build_time_reqs branch from c9621b7 to fadb614 Compare January 2, 2018 21:29
@msarahan msarahan merged commit db7f1e0 into conda:master Jan 2, 2018
@msarahan msarahan deleted the fix_run_exports_not_applying_in_build_time_reqs branch January 2, 2018 22:52
@github-actions
Copy link

Hi there, thank you for your contribution!

This pull request has been automatically locked because it has not had recent activity after being closed.

Please open a new issue or pull request if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Apr 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Behaviour of run_exports has changed? strong run_exports not crossing boundaries?
1 participant