You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: RELEASE.md
+7-38
Original file line number
Diff line number
Diff line change
@@ -45,52 +45,21 @@ npm publish --access public
45
45
46
46
## Automated releases with the Jupyter Releaser
47
47
48
-
The extension repository should already be compatible with the Jupyter Releaser.
49
-
50
-
Check out the [workflow documentation](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html) for more information.
48
+
The extension repository should already be compatible with the Jupyter Releaser. But
49
+
the GitHub repository and the package managers need to be properly set up. Please
50
+
follow the instructions of the Jupyter Releaser [checklist](https://jupyter-releaser.readthedocs.io/en/latest/how_to_guides/convert_repo_from_repo.html).
51
51
52
52
Here is a summary of the steps to cut a new release:
53
53
54
-
- Add tokens to the [Github Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) in the repository:
55
-
-`ADMIN_GITHUB_TOKEN` (with "public_repo" and "repo:status" permissions); see the [documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
56
-
-`NPM_TOKEN` (with "automation" permission); see the [documentation](https://docs.npmjs.com/creating-and-viewing-access-tokens)
- Set up your PyPI project by [adding a trusted publisher](https://docs.pypi.org/trusted-publishers/adding-a-publisher/)
62
-
- The _workflow name_ is `publish-release.yml` and the _environment_ should be left blank.
63
-
- Ensure the publish release job as `permissions`: `id-token : write` (see the [documentation](https://docs.pypi.org/trusted-publishers/using-a-publisher/))
- If the repo generates PyPI release(s), create a scoped PyPI [token](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#saving-credentials-on-github). We recommend using a scoped token for security reasons.
70
-
71
-
- You can store the token as `PYPI_TOKEN` in your fork's `Secrets`.
72
-
73
-
- Advanced usage: if you are releasing multiple repos, you can create a secret named `PYPI_TOKEN_MAP` instead of `PYPI_TOKEN` that is formatted as follows:
74
-
75
-
```text
76
-
owner1/repo1,token1
77
-
owner2/repo2,token2
78
-
```
79
-
80
-
If you have multiple Python packages in the same repository, you can point to them as follows:
81
-
82
-
```text
83
-
owner1/repo1/path/to/package1,token1
84
-
owner1/repo1/path/to/package2,token2
85
-
```
86
-
87
-
</details>
88
-
89
54
- Go to the Actions panel
90
55
- Run the "Step 1: Prep Release" workflow
91
56
- Check the draft changelog
92
57
- Run the "Step 2: Publish Release" workflow
93
58
59
+
> [!NOTE]
60
+
> Check out the [workflow documentation](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html)
61
+
> for more information.
62
+
94
63
## Publishing to `conda-forge`
95
64
96
65
If the package is not on conda forge yet, check the documentation to learn how to add it: https://conda-forge.org/docs/maintainer/adding_pkgs.html
0 commit comments