Release v0.13.9

.github/workflows/changelog.yml

@@ -13,4 +13,6 @@ on:
 
 jobs:
   call-changelog-check-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.21.1
+    permissions:
+      contents: read

.github/workflows/check-links.yml

@@ -9,11 +9,11 @@ jobs:
   linkChecker:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
       - name: Link Checker
         id: lychee
-        uses: lycheeverse/lychee-action@v2.7.0
+        uses: lycheeverse/lychee-action@v2.8.0
         env:
           GITHUB_TOKEN: ${{secrets.TOOLS_BOT_PAK}}
         with:

.github/workflows/create-jira-issue.yml

@@ -6,7 +6,9 @@ on:
 
 jobs:
   call-create-jira-issue-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.21.1
+    permissions:
+      issues: write
     secrets:
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
       JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}

.github/workflows/deploy_to_github_io.yml

@@ -11,11 +11,11 @@ jobs:
     name: Build site and deploy
     runs-on: "ubuntu-latest"
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
         with:
           path: hyp3-docs
 
-      - uses: conda-incubator/setup-miniconda@v3
+      - uses: conda-incubator/setup-miniconda@v4
         with:
           auto-update-conda: true
           python-version: '3.10'
@@ -33,7 +33,7 @@ jobs:
           sed -i 's|site_url: https://hyp3-docs.asf.alaska.edu/|site_url: https://hyp3-docs.asf.alaska.edu/hyp3-docs/|' mkdocs.yml
           mkdocs gh-deploy --force
 
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
         if: github.ref == 'refs/heads/main'
         with:
           repository: ASFHyP3/ASFHyP3.github.io

.github/workflows/labeled-pr.yml

@@ -12,4 +12,6 @@ on:
 
 jobs:
   call-labeled-pr-check-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.21.1
+    permissions:
+      pull-requests: read

.github/workflows/release-template-comment.yml

@@ -7,6 +7,8 @@ on:
 
 jobs:
   call-release-checklist-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.21.1
+    permissions:
+      pull-requests: write
     secrets:
       USER_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release.yml

@@ -7,7 +7,8 @@ on:
 
 jobs:
   call-release-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.21.1
+    permissions: {}
     with:
       release_prefix: HyP3 Docs
     secrets:

.github/workflows/spellcheck.yml

@@ -7,7 +7,7 @@ jobs:
     name: Spellcheck
     steps:
       - name: Checkout
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
       - name: Spellcheck
         uses: tbroadley/spellchecker-cli-action@v1
         with:
@@ -19,7 +19,7 @@ jobs:
           plugins: "spell repeated-words syntax-mentions syntax-urls frontmatter"
       - name: Report
         if: ${{ failure() }}
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v7
         with:
           name: report
           path: report.json

.github/workflows/static-analysis.yml

@@ -4,4 +4,6 @@ on: push
 
 jobs:
   call-secrets-analysis-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.21.1
+    permissions:
+      contents: read

.github/workflows/tag-release.yml

@@ -7,6 +7,7 @@ on:
 
 jobs:
   call-bump-version-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.20.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.21.1
+    permissions: {}
     secrets:
       USER_TOKEN: ${{ secrets.TOOLS_BOT_PAK }}

.github/workflows/test-build.yml

@@ -11,9 +11,9 @@ jobs:
     name: Test build of site
     runs-on: "ubuntu-latest"
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
 
-      - uses: conda-incubator/setup-miniconda@v3
+      - uses: conda-incubator/setup-miniconda@v4
         with:
           auto-update-conda: true
           python-version: '3.10'

.github/workflows/update_asf_tools_version.yml

@@ -12,7 +12,7 @@ jobs:
     name: Bump the ASF Tools version
     runs-on: "ubuntu-latest"
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
         with:
           token: ${{ secrets.TOOLS_BOT_PAK }}
 

.github/workflows/update_sdk_version.yml

@@ -12,7 +12,7 @@ jobs:
     name: Bump the SDK version
     runs-on: "ubuntu-latest"
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
         with:
           token: ${{ secrets.TOOLS_BOT_PAK }}
 

CHANGELOG.md

@@ -6,6 +6,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [PEP 440](https://www.python.org/dev/peps/pep-0440/)
 and uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+
+## [0.13.9]
+
+### Changed
+* Updated product guide naming conventions to include Sentinel-1D mission identifiers
+* Documented lack of support for Sentinel-1D acquisitions in ISCE2 software
+
 ## [0.13.8]
 
 ### Changed

docs/guides/burst_insar_product_guide.md

@@ -21,11 +21,15 @@ For those who would prefer to work at the scale of a full IW SLC, our original
 [On Demand InSAR](insar_product_guide.md){target=_blank} products are still available. These products have a larger 
 footprint, and are generated using [GAMMA software](https://www.gamma-rs.ch/software){target=_blank}.  If unsure of which InSAR processing option best fits your needs, visit our [ASF Sentinel-1 InSAR on Demand Product Comparison StoryMap](https://storymaps.arcgis.com/stories/6cb4f1c18558441bb9b4b11337515b53 "ASF Sentinel-1 InSAR On Demand Product Comparison"){target=_blank} to explore the capabilities, characteristics, and available products for each of ASF's On Demand InSAR options. 
 
-!!! tip "Sentinel-1C acquisitions now supported!" 
+!!! tip "Sentinel-1D acquisitions not yet supported" 
 
-    ISCE2 has been updated to support processing of data collected by Sentinel-1C. Users can now submit 
-    burst-based InSAR jobs for any available bursts from Sentinel-1 IW SLCs, regardless of the platform used 
-    to acquire the data.
+    ISCE2 software does not currently support processing Sentinel-1D acquisitions. Until the software package is 
+    updated, users will not be able to include Sentinel-1D bursts in pairs submitted for Burst InSAR 
+    processing. 
+
+    Users can submit full IW Sentinel-1D granules for processing to InSAR using the 
+    [On Demand InSAR](insar_product_guide.md "Sentinel-1 InSAR Product Guide") option, which leverages 
+    GAMMA software rather than ISCE2. 
 
 ## Burst InSAR Job Types
 

docs/guides/gunw_product_guide.md

@@ -103,6 +103,12 @@ ARIA-S1-GUNW jobs for On Demand processing.
 If the ARIA-S1-GUNW products you need are not available in the archive, you can use ASF's On Demand platform to submit 
 custom ARIA-S1-GUNW jobs for processing. 
 
+!!! warning "Sentinel-1D acquisitions not yet supported" 
+
+    ISCE2 software, which is used for processing ARIA GUNW products, does not currently support processing 
+    SLCs acquired by the newly launched Sentinel-1D platform. Until the software package is updated, users will 
+    not be able to submit ARIA-S1-GUNW jobs that include Sentinel-1D acquisitions for On-Demand processing.
+
 To order ARIA-S1-GUNW products using 
 [Vertex](https://search.asf.alaska.edu/#/?dataset=SENTINEL-1%20INTERFEROGRAM%20(BETA)), 
 select **ARIA-S1-GUNW** from the Dataset menu for a **Geographic Search**, and turn on the **On Demand** toggle switch. 

docs/guides/insar_product_guide.md

@@ -218,9 +218,9 @@ HyP3 InSAR output is a zip file containing various files, including GeoTIFFs, PN
 The InSAR product names are packed with information pertaining to the processing of the data, presented in the 
 following order, as illustrated in Figure 4. 
 
-- The platform names, one of Sentinel-1A, Sentinel-1B, or Sentinel-1C, are abbreviated with the letters `A`, `B`, or `C`
+- The platform names, one of Sentinel-1A, Sentinel-1B, Sentinel-1C, or Sentinel-1D, are abbreviated with the letters `A`, `B`, `C`, or `D`
     - Two of these letters follow `S1`, indicating the platform(s) used to acquire the reference and 
-      secondary images, in that order (`S1AA`, `S1BA`, `S1AC`, etc.)
+      secondary images, in that order (`S1AA`, `S1BA`, `S1AC`, `S1CD`, etc.)
 - The reference start date and time and the secondary start date and time, with the date and time 
   separated by the letter T
 - The polarizations for the pair, either HH or VV, the orbit type, and the days of separation for the pair

docs/guides/insar_product_guide_template.md

@@ -71,12 +71,11 @@ Jobs can be submitted for processing using the
 [HyP3 Python SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/ "https://hyp3-docs.asf.alaska.edu/using/sdk" ){target=_blank} 
 or the [HyP3 API](https://hyp3-docs.asf.alaska.edu/using/api/ "https://hyp3-docs.asf.alaska.edu/using/api" ){target=_blank}.
 
-!!! tip "InSAR Processing Now Supports Sentinel-1C!" 
+!!! warning "Sentinel-1D Support for InSAR Processing" 
 
-    GAMMA and ISCE2 software have both been updated to support Sentinel-1C acquisitions as input for InSAR processing. 
-    Users can now use any Sentinel-1 IW SLCs in the archive, including those acquired by Sentinel-1C, as input for 
-    either [On Demand InSAR](insar_product_guide.md) or [On Demand Burst InSAR](burst_insar_product_guide.md) 
-    processing.
+    GAMMA software supports Sentinel-1D acquisitions as input for InSAR processing, but ISCE2 software currently does 
+    not. Until ISCE2 is updated, users will only be able to submit jobs including Sentinel-1D SLCs for processing 
+    using [On Demand InSAR](insar_product_guide.md), not [On Demand Burst InSAR](burst_insar_product_guide.md).
 
 ### Vertex
 InSAR pairs are selected in [Vertex](https://search.asf.alaska.edu/#/ "https://search.asf.alaska.edu" ){target=_blank} using either the [Baseline Search](https://docs.asf.alaska.edu/vertex/baseline/ "https://docs.asf.alaska.edu/vertex/baseline" ){target=_blank} or the [SBAS Search](https://docs.asf.alaska.edu/vertex/sbas/ "https://docs.asf.alaska.edu/vertex/sbas" ){target=_blank} interface. The process of selecting pairs is the same for both IW SLC products and individual SLC bursts, but you will need to select the appropriate dataset when searching for content. As illustrated below, select the **Sentinel-1** option in the Dataset menu to search for IW SLC products, and select the **S1 Bursts** option to search for individual SLC bursts.

docs/guides/rtc_product_guide.md

@@ -261,7 +261,7 @@ Example: S1A_IW_20180128T161201_DVP_RTC30_G_gpuned_FD6A
 
 | Element  | Definition                                                                   | Example  |
 |----------|------------------------------------------------------------------------------|----------|
-| x        | Sentinel-1 Platform: A, B, or C                                              | A        |
+| x        | Sentinel-1 Platform: A, B, C, or D                                           | A        |
 | yy       | Beam Mode                                                                    | IW       |
 | aaaaaaaa | Start Year-Month-Day                                                         | 20180128 |
 | bbbbbb   | Start Hour-Minute-Second                                                     | 161201   |

docs/products.md

@@ -115,6 +115,16 @@ sets of up to 15 contiguous along-track bursts to generate a single output inter
 [Sentinel-1 Burst InSAR Product Guide](guides/burst_insar_product_guide.md "Sentinel-1 Burst InSAR Product Guide") 
 for more information.
 
+!!! warning "Sentinel-1D acquisitions not yet supported in ISCE2" 
+
+    ISCE2 software does not currently support processing Sentinel-1D acquisitions. Until the software package is 
+    updated, users will not be able to include Sentinel-1D bursts in pairs submitted for Burst InSAR 
+    processing. 
+
+    Users can submit full IW Sentinel-1D granules for processing to InSAR using the 
+    [On Demand InSAR](insar_product_guide.md "Sentinel-1 InSAR Product Guide") option, which leverages 
+    GAMMA software rather than ISCE2. 
+
 For step-by-step instructions on searching for, ordering and downloading On Demand Burst InSAR products, visit our 
 [Burst-Based InSAR for Sentinel-1 On Demand](https://storymaps.arcgis.com/stories/191bf1b6962c402086807390b3ce63b0 "Burst-Based InSAR for Sentinel-1 On Demand StoryMap" ){target=_blank} 
 tutorial.