Skip to content

Conversation

lucyleeow
Copy link
Collaborator

References and relevant issues

Possible f i x es #283

Description

Add constraints as env variable to the build step of 'deploy_docs' workflow, matching the 'build_docs' workflow.

(no further improvement of these workflows attempted in this PR, they can be done later, see #284)

Copy link
Member

@psobolewskiPhD psobolewskiPhD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should merge sooner rather than later to see if this has any impact on the issue.

@lucyleeow
Copy link
Collaborator Author

Agreed, would be great for this to go in!

@psobolewskiPhD psobolewskiPhD added this to the 0.5.0 milestone Dec 4, 2023
@psobolewskiPhD psobolewskiPhD merged commit 53a292f into napari:main Dec 4, 2023
@psobolewskiPhD
Copy link
Member

Merged, lets see what happens on deployment!

@lucyleeow lucyleeow deleted the ci_constraint branch December 5, 2023 00:10
melissawm pushed a commit that referenced this pull request Dec 5, 2023
# References and relevant issues
Fix failing deployment:
https://github.com/napari/docs/actions/runs/7093394130/job/19306680514
caused by #287

# Description
In the deploy workflow, napari is cloned into napari-repo:
`path: napari-repo  # place in a named directory`
fixing that here so that the constraints path in the ENV variable is
also using napari-repo and not napari.
Obviously overlooked this difference when reviewing
#287
Yet another reason to use just one workflow,
#284
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants