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

safer publish way #5

Merged
merged 2 commits into from
May 11, 2023
Merged

safer publish way #5

merged 2 commits into from
May 11, 2023

Conversation

Czaki
Copy link
Contributor

@Czaki Czaki commented May 11, 2023

Recently pypi has implemented a safer way for publishing python package releases without the need to generate and provide tokens. It requires correct implementation in publishing section of project settings on pypi.

obraz

I have already implemented this in this project and it works:
https://github.com/Czaki/local-migrator/blob/8cb1a62d6520f0a33d8190c88ec737ea72d9b6d6/.github/workflows/tests.yml#L84-L108

@codecov
Copy link

codecov bot commented May 11, 2023

Codecov Report

Merging #5 (fd8cbbe) into main (76e8725) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   90.65%   90.65%           
=======================================
  Files           5        5           
  Lines        1166     1166           
=======================================
  Hits         1057     1057           
  Misses        109      109           

@jaimergp
Copy link
Contributor

Thank you, I added the pertinent data in PyPI now.

@jaimergp jaimergp merged commit 566f2a2 into napari:main May 11, 2023
@Czaki Czaki deleted the pypi_publish branch July 26, 2023 09:26
@goanpeca goanpeca added the task Work around tooling / release / ci label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Work around tooling / release / ci
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants