Update the instructions for updating the conda package

.github/ISSUE_TEMPLATE/release_checklist.md

@@ -29,7 +29,7 @@ git push --tags
 - [ ] Commit changes to Github
 
 **3rd party update**:
-- [ ] Update conda-forge [pygmt-feedstock](https://github.com/conda-forge/pygmt-feedstock)
+- [ ] Update conda-forge [pygmt-feedstock](https://github.com/conda-forge/pygmt-feedstock) [Usually done automatically by conda-forge's bot]
 
 ---
 

MAINTENANCE.md

@@ -152,17 +152,18 @@ this new folder.
 Grab a zip file from the Github release and upload to Zenodo using the previously
 reserved DOI.
 
-### Updating the conda package (Not available yet)
+### Updating the conda package
 
-After Travis is done building the tag and all builds pass, we need to update the conda
-package.
-Unfortunately, this needs to be done manually for now.
+When a new version is released on PyPI, conda-forge's bot automatically creates version
+updates for the feedstock. In most cases, the maintainers can simply merge that PR.
 
-1. Fork the feedstock repository (https://github.com/conda-forge/pygmt-feedstock) if
+If changes are needed to be done manually, you can:
+
+1. Fork the [pygmt feedstock repository](https://github.com/conda-forge/pygmt-feedstock) if
    you haven't already. If you have a fork, update it.
 2. Update the version number and sha256 hash on `recipe/meta.yaml`. You can get the hash
    from the PyPI "Download files" section.
 3. Add or remove any new dependencies (most are probably only `run` dependencies).
 4. Make a new branch, commit, and push your changes **to your fork**.
 5. Create a PR against the original feedstock master.
-6. Once the CIs are passing, merge or as a maintainer to do so.
+6. Once the CIs are passing, merge the PR or ask a maintainer to do so.