Merge branch 'main' into cgarling-patch-1

Author: icweaver

.github/workflows/CI.yml

@@ -21,7 +21,7 @@ jobs:
         arch:
           - x64
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
       - uses: julia-actions/setup-julia@v2
         with:
           version: ${{ matrix.version }}

.github/workflows/DocPreviewCleanup.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout gh-pages branch
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           ref: gh-pages
 
@@ -21,7 +21,7 @@ jobs:
       - uses: julia-actions/cache@v2
 
       - name: Check for stale PR previews
-        shell: julia {0}
+        shell: julia --color=yes {0}
         run: |
           using Pkg
           Pkg.activate(temp = true)
@@ -39,8 +39,8 @@ jobs:
           end
 
           function all_prs()
-              url = "https://api.github.com/repos/$repo/pulls?per_page=100;page=$(page)"
-              query_prs(page) = JSON3.read(HTTP.get(url).body)
+              url = "https://api.github.com/repos/$repo/pulls?per_page=100;page="
+              query_prs(page) = JSON3.read(HTTP.get(url * string(page)).body)
               prs = []
               page = 1
               while true
@@ -62,15 +62,18 @@ jobs:
 
           if isempty(stale_previews)
               @info "No stale previews"
-              exit(1)
+              println(ENV["GITHUB_ENV"], "FOUND_STALE_PREVIEWS=false")
+              exit()
           end
+          println(ENV["GITHUB_ENV"], "FOUND_STALE_PREVIEWS=true")
 
           for pr in stale_previews
               path = joinpath("previews", "PR$pr")
               @info "Removing $path"
               run(`git rm -rf $path`)
           end
       - name: Push changes
+        if: ${{ env.FOUND_STALE_PREVIEWS == 'true' }}
         run: |
           git config user.name "Documenter.jl"
           git config user.email "[email protected]"

.github/workflows/Documentation.yml

@@ -10,7 +10,7 @@ jobs:
     name: MultiDocumentation
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
       - uses: julia-actions/setup-julia@v2
         with:
           version: "1"

README.md

@@ -46,9 +46,9 @@ Below we walk through three main ways to contribute to the JuliaAstro site:
 
 Typo fixes or suggested changes to existing prose is appreciated! The most direct way to create a PR is to navigate to the page that you would like to edit, and select the "Edit source on GitHub" icon that appears at the top of each page. From there, you can submit your edits as usual following [the GitHub guide for submitting in-browser changes](https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files).
 
-### 2. Adding a package to our [Ecosystems page](https://juliaastro.org/home/ecosystem/) or [Comparison to Astropy page](https://juliaastro.org/home/comparison/)
+### 2. Adding a package to our [Package Ecosystem page](https://juliaastro.org/home/ecosystem/) or [Comparison to Astropy page](https://juliaastro.org/home/comparison/)
 
-Our Ecosystem page and Comparison page are integrated with the rest of the site, including the global navbar dropdown menu across the top, and in our [integration testing suite](https://github.com/JuliaAstro/JuliaAstro.github.io/actions/workflows/CI.yml). To add a package, include an entry in [`src/JuliaAstroDocs.jl`](https://github.com/JuliaAstro/JuliaAstro.github.io/blob/main/src/JuliaAstroDocs.jl), following the same format as the other packages. Below is an example entry of how that might look:
+Our Package Ecosystem page and Comparison page are integrated with the rest of the site, including the global navbar dropdown menu across the top, and in our [integration testing suite](https://github.com/JuliaAstro/JuliaAstro.github.io/actions/workflows/CI.yml). To add a package, include an entry in [`src/JuliaAstroDocs.jl`](https://github.com/JuliaAstro/JuliaAstro.github.io/blob/main/src/JuliaAstroDocs.jl), following the same format as the other packages. Below is an example entry of how that might look:
 
 ```julia
   (
@@ -116,3 +116,4 @@ The `include_dirs` arg allows our internal Revise worklow to pick up changes in
 > If just making simple markdown changes, you can shorten the build time between edits by commenting out the call to `MultiDocumenter.make` in [`docs/make.jl`](https://github.com/JuliaAstro/JuliaAstro.github.io/blob/main/docs/make.jl). This disables the MultiDocumenter.jl repo-cloning and top navbar build process, and can be done without needing to restart your `LiveServer` session.
 
 See our [Contributing page](https://juliaastro.org/home/#Contributing) for more.
+

docs/make.jl

@@ -87,7 +87,7 @@ makedocs(
                 "tutorials/curve-fit.md",
             ],
         ],
-        "Ecosystem" => "ecosystem.md",
+        "Package Ecosystem" => "ecosystem.md",
         "Comparison with Astropy" => "comparison.md",
         case_studies,
     ],

docs/src/index.md

@@ -1,6 +1,6 @@
 # JuliaAstro
 
-[JuliaAstro](https://github.com/JuliaAstro) and its affiliated organizations are a community for astronomy in Julia. We have a wide variety of packages from [aperture photometry](https://github.com/juliaastro/Photometry.jl) to [cosmology](https://github.com/juliaastro/Cosmology.jl). Check out a curated list of packages in the JuliaAstro ecosystem (and beyond) on the [Ecosystem page](@ref eco), or visit their documentation directly via the navbar above. Pure Julia packages are marked with a closed circle ⬤, while wrapper packages for other languages are marked with an open circle ◯. 
+[JuliaAstro](https://github.com/JuliaAstro) and its affiliated organizations are a community for astronomy in Julia. We have a wide variety of packages from [aperture photometry](https://github.com/juliaastro/Photometry.jl) to [cosmology](https://github.com/juliaastro/Cosmology.jl). Check out a curated list of packages in the JuliaAstro ecosystem (and beyond) on the [Package Ecosystem page](@ref eco), or visit their documentation directly via the navbar above. Pure Julia packages are marked with a closed circle ⬤, while wrapper packages for other languages are marked with an open circle ◯. 
 
 ## Contributing
 
@@ -63,20 +63,18 @@ Would you like to contribute to JuliaAstro through Google Summer of Code? You ca
     - Trajectory optimisation in space mechanics with Julia [[pretalx]](https://pretalx.com/juliacon2024/talk/UXJWXS/) [[video]](https://www.youtube.com/watch?v=a4-wynFTCmk)
     - Propagating large orbital uncertainty with TaylorIntegration.jl [[pretalx]](https://pretalx.com/juliacon2024/talk/SQFY3B/) [[video]](https://www.youtube.com/watch?v=G6uzqwDZCwA)
 
-### Upcoming
-
 !!! details "JuliaCon 2025"
     **Julia in Astronomy & Astrophysics Research Symposium 2025 [[website]](https://eford.github.io/AstroMiniSymposiumAtJuliaCon2025/)**
     - [Building an Astronomy Code for VLBI in Julia](https://pretalx.com/juliacon-2025/talk/NSZLHS/)
-    - [Instrument Modelling for Radio Telescopes with Julia](https://pretalx.com/juliacon-2025/talk/Q7XZBZ/)
-    - Bayesian Multifrequency Imaging for Radio Astronomy (TBC)
+    - [Astrometry.jl: A Fundamental Julia Package for Astronomy](https://pretalx.com/juliacon-2025/talk/SGJEKU/)
+    - [Bayesian Multifrequency Imaging for Radio Astronomy](https://pretalx.com/juliacon-2025/talk/BNCPT8/)
     - [Regularized Maximum Likelihood Methods for Black Hole Imaging](https://pretalx.com/juliacon-2025/talk/AYBT3G/)
-    - Space time and accretion inference from images of black holes (TBC)
+    - [Krang.jl: Physics inference from images fo Black Holes](https://pretalx.com/juliacon-2025/talk/GCSQQC/)
     - [Building an End-to-End Spectral Reduction Pipeline for APOGEE](https://pretalx.com/juliacon-2025/talk/HYYXTA/)
     - [Juggling astro catalogs in Julia: convenience meets performance](https://pretalx.com/juliacon-2025/talk/TUXFSL/)
     - [ScatteringOptics.jl: An Interstellar Scattering Framework](https://pretalx.com/juliacon-2025/talk/N7ZEMF/)
-    - Astrometry.jl: A Fundamental Julia Package for Astronomy (TBC)
-    - Panel Discussion (TBC)
+    - [Panel Discussion](https://pretalx.com/juliacon-2025/talk/EWRB37/)
 
     **More aero/astro talks at JuliaCon**
     - [Tuning attitude control gains of a satellite using Julia](https://pretalx.com/juliacon-2025/talk/SAYCCZ/)
+    - [Interfacing Julia with Kerbal Space Program using KRPC.jl](https://pretalx.com/juliacon-2025/talk/3YTQY7/)

docs/src/tutorials/index.md

@@ -4,7 +4,7 @@ Welcome! This page contains links to general tutorials useful to astronomers and
 
 In Julia, smaller focussed packages are preferred. This page shows how you can combine smaller packages to get big results!
 
-For more advanced usage examples, please see the documentation pages of the individual packages linked on the [Ecosystem](@ref eco) page.
+For more advanced usage examples, please see the documentation pages of the individual packages linked on the [Package Ecosystem](@ref eco) page.
 
 
 ## Installing Julia

src/JuliaAstroDocs.jl

@@ -784,6 +784,16 @@ ecosystem() = (
             ),
         ),
         "Data processing" => (
+            (
+                name = "Astroalign.jl",
+                repo = "https://github.com/JuliaAstro/Astroalign.jl",
+                doc = "https://juliaastro.org/Astroalign/stable/",
+                tagline = "An experimental reimplementation of astroalign.py",
+                descr = """
+                - An experimental reimplementation of [astroalign](https://github.com/quatrope/astroalign) in Julia
+                """,
+                astropy = ["astroalign"],
+            ),
             (
                 name = "torrance/Casacore.jl",
                 repo = "https://github.com/torrance/Casacore.jl",

src/ecosystem.jl

@@ -1,5 +1,5 @@
 const ECOSYSTEM_HEADER = """
-# [Ecosystem](@id eco)
+# [Package Ecosystem](@id eco)
 
 The joy of our community is the many astronomy and astrophysics packages available for wide use. Packages are separated by functionality and Julia's declarative package manager takes care of resolving dependencies. You get just the functionality you need, and smaller packages lead to more rapid development.