-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adds releaser #10
Adds releaser #10
Conversation
uses: jupyterlab/maintainer-tools/.github/actions/base-setup@v1 | ||
- name: Install Dependencies | ||
run: | | ||
pip install -e . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally it would be better to remove this step as it is not needed anymore with releaser v2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having a pip install -e .
only in the check release workflow but not in the "Publish Release" workflow (the one used to do the real release) can add unexpected side effects (some dev dependencies missing in the actual release workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jtpio
No description provided.