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: fern/products/sdks/overview/python/publishing-to-pypi.mdx
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ You'll need to update your `generators.yml` file to configure the package name,
32
32
33
33
In the `group` for your Python SDK, change the output location in from `local-file-system` (the default) to `pypi` to indicate that Fern should publish your package directly to the PyPi registry:
34
34
35
-
```yaml title="Python" {6-7}
35
+
```yaml title="generators.yml" {6-7}
36
36
groups:
37
37
python-sdk:
38
38
generators:
@@ -49,7 +49,7 @@ You'll need to update your `generators.yml` file to configure the package name,
49
49
Your package name must be unique in the PyPI repository, otherwise publishing your SDK to PyPI will fail.
50
50
51
51
52
-
```yaml title="Python" {8}
52
+
```yaml title="generators.yml" {8}
53
53
groups:
54
54
python-sdk:
55
55
generators:
@@ -67,7 +67,7 @@ groups:
67
67
The `client-class-name` option controls the name of the generated client. This is the name customers use to import your SDK (`import { your-client-name } from 'your-package-name';`).
68
68
69
69
70
-
```yaml title="Python" {9-10}
70
+
```yaml title="generators.yml" {9-10}
71
71
groups:
72
72
python-sdk:
73
73
generators:
@@ -124,7 +124,7 @@ groups:
124
124
125
125
Add the path to your GitHub repository to `generators.yml`:
Copy file name to clipboardExpand all lines: fern/products/sdks/snippets/release-sdk.mdx
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,4 @@ The rest of the release process depends on your chosen mode:
2
2
3
3
-**Release mode (default):** If you didn't specify a `mode` or set `mode: release`, no further action is required. Fern automatically tags the new release with your specified version number and initiates the npm publishing workflow in your SDK repository.
4
4
5
-
-**Pull request or push mode:** If you set `mode: pull-request` or `mode: push`, Fern creates a pull request or pushes to a branch respectively. Review and merge the PR (`pull-request`) or branch (`push`), then [tag a new release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) to initiate the npm publishing workflow in your SDK repository.
6
-
7
-
Once the workflow completes, you can view your new release by logging into npm and navigating to **Packages**.
5
+
-**Pull request or push mode:** If you set `mode: pull-request` or `mode: push`, Fern creates a pull request or pushes to a branch respectively. Review and merge the PR (`pull-request`) or branch (`push`), then [tag a new release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) to initiate the npm publishing workflow in your SDK repository.
0 commit comments