-
Notifications
You must be signed in to change notification settings - Fork 115
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
Adopt jupyter-releaser #114
Conversation
Thanks, @ihuicatl! It would be interesting to add the GitHub action check-release. This way, we could see what is missing. |
After updating the MANIFEST, |
3491e6c
to
7bd2179
Compare
I added the GitHub action to check-release. Now the issue is with
which comes from Still need to update the pyproject.toml file. |
67086d6
to
28a97d4
Compare
c239591
to
93c60a9
Compare
This changes the configuration to be able to use jupyter-releaser by following the instructions given in Convert a Repo to Use Releaser.
When tested locally, this command succeeds with some warnings
However, this fails
with the following (truncated) output message:
No GitHub Actions have been created yet to check the release.