Merge pull request #32 from ocefpaf/fix_link

Fix link
ioos · Oct 4, 2024 · 11b2031 · 11b2031
2 parents 83a7ede + 38598ec
commit 11b2031
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 4 deletions.
diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml
@@ -20,7 +20,7 @@ jobs:
         fetch-depth: 0
 
     - name: Setup Micromamba
-      uses: mamba-org/setup-micromamba@v1
+      uses: mamba-org/setup-micromamba@v2
       with:
         environment-name: TEST
         init-shell: bash

diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
@@ -20,7 +20,7 @@ jobs:
         fetch-depth: 0
 
     - name: Setup Micromamba ${{ matrix.python-version }}
-      uses: mamba-org/setup-micromamba@v1
+      uses: mamba-org/setup-micromamba@v2
       with:
         environment-name: TEST
         init-shell: bash

diff --git a/docs/source/how2package4ioos.md b/docs/source/how2package4ioos.md
@@ -71,8 +71,6 @@ The main advantages of using these PEPs together are:
 - ensure that setup dependencies will be available at build time.
 
 
-[This blog post](https://chadsmith-software.medium.com/pep-517-and-518-in-plain-english-47208ca8b7a6) contains a nice summary of these PEPs.
-
 For IOOS packages we recommend to keep a bare bones `setup.py`,
 for backwards compatibility, and to move all the package metadata to a `setup.cfg`,
 while keeping the `pyproject.toml` only for the build information.