@@ -69,23 +69,24 @@ Steps to release a new version:
69
69
These steps are from the general process described in https://conda-forge.org/docs/maintainer/updating_pkgs.html
70
70
71
71
** A. Setup local repo and branch for the update**
72
+
72
73
1 . Fork repo https://github.com/conda-forge/text_extensions_for_pandas-feedstock
73
74
2 . Clone fork as origin and add upstream remote
74
75
3 . Fetch and rebase local master with upstream/master
75
76
4 . Make branch e.g. update_0_1_b3
76
77
77
78
** B. Edit and test the recipe file**
78
- 5 . Edit recipe/meta.yaml
79
- 6 . Update version string
80
- 7 . Download source code tar.gz file (link with "archive" ~ 23MB)from github release and run:
79
+ 1 . Edit recipe/meta.yaml
80
+ 1 . Update version string
81
+ 1 . Download source code tar.gz file (link with "archive" ~ 23MB)from github release and run:
81
82
openssl sha256 path/to/text_extensions_for_pandas-0.1b3.tar.gz
82
83
update source/sha256 hash string in recipe
83
- 8 . Update dependency info to match requirements.txt
84
- 9 . Bump the build number if version is unchanged, reset build number to 0 if version is changed
85
- 10 . Test changes locally with "python build-locally.py" (requires Docker)
84
+ 1 . Update dependency info to match requirements.txt
85
+ 1 . Bump the build number if version is unchanged, reset build number to 0 if version is changed
86
+ 1 . Test changes locally with "python build-locally.py" (requires Docker)
86
87
87
88
** C. Push changes to the forked repo and make a PR**
88
- 11 . Follow instructions and checklist in PR
89
- 12 . Wait for checks to pass
90
- 13 . Merge PR to master branch, using Github interface is fine
91
- 14 . Once merged, the conda package will be created automatically
89
+ 1 . Follow instructions and checklist in PR
90
+ 1 . Wait for checks to pass
91
+ 1 . Merge PR to master branch, using Github interface is fine
92
+ 1 . Once merged, the conda package will be created automatically
0 commit comments