Merge branch 'develop' into feat/action-versioning

dandelany · web-flow · commit d9a41344010a · 2026-04-07T17:12:23.000-07:00
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,5 +1,5 @@
 Please help us process issues more efficiently by filing an issue using one of the following templates:
 
-https://github.com/NASA-AMMOS/aerie/issues/new/choose
+https://github.com/NASA-AMMOS/plandev/issues/new/choose
 
 Thank you!
diff --git a/.github/ISSUE_TEMPLATE/2-feature_request.yml b/.github/ISSUE_TEMPLATE/2-feature_request.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thanks for taking the time to request this feature! If your feature request is complex or substantial enough to warrant in-depth discussion, maintainers may close the issue and ask you to open a [Discussion](https://github.com/NASA-AMMOS/aerie/discussions).
+        Thanks for taking the time to request this feature! If your feature request is complex or substantial enough to warrant in-depth discussion, maintainers may close the issue and ask you to open a [Discussion](https://github.com/NASA-AMMOS/plandev/discussions).
   - type: dropdown
     id: checked-for-duplicates
     attributes:
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: PlanDev UI
-    url: https://github.com/NASA-AMMOS/aerie-ui/issues/new/choose
+    url: https://github.com/NASA-AMMOS/plandev-ui/issues/new/choose
     about: Issues and feature requests for the PlanDev UI repo (not backend related).
   - name: PlanDev Docs
     url: https://github.com/NASA-AMMOS/plandev-docs/issues/new/choose
diff --git a/.github/config/.trivyignore b/.github/config/.trivyignore
@@ -5,7 +5,7 @@
 # which is installed by the postgres docker container and does not use the entirety of the Go stdlib
 # for details see:
 # - https://github.com/tianon/gosu/blob/master/SECURITY.md
-# - https://github.com/NASA-AMMOS/aerie/pull/1546
+# - https://github.com/NASA-AMMOS/plandev/pull/1546
 # - https://github.com/tianon/gosu/pull/173#issuecomment-3936440684
 CVE-2023-24538
 CVE-2023-24540
diff --git a/README.md b/README.md
@@ -88,5 +88,5 @@ The scripts and documentation in this project are released under the [MIT Licens
 [deployment]: ./deployment
 [dev]: ./docs/DEVELOPER.md
 [fast-track]: https://nasa-ammos.github.io/plandev-docs/introduction/#fast-track
-[ui-repo]: https://github.com/NASA-AMMOS/aerie-ui
+[ui-repo]: https://github.com/NASA-AMMOS/plandev-ui
 
diff --git a/deployment/Environment.md b/deployment/Environment.md
@@ -13,7 +13,7 @@ This document provides detailed information about environment variables for each
 
 ## PlanDev Gateway
 
-See the [environment variables document](https://github.com/NASA-AMMOS/aerie-gateway/blob/develop/docs/ENVIRONMENT.md) in the PlanDev Gateway repository.
+See the [environment variables document](https://github.com/NASA-AMMOS/plandev-gateway/blob/develop/docs/ENVIRONMENT.md) in the PlanDev Gateway repository.
 
 ## PlanDev Merlin
 
@@ -105,7 +105,7 @@ See the [environment variables document](https://github.com/NASA-AMMOS/aerie-gat
 
 ## PlanDev UI
 
-See the [environment variables document](https://github.com/NASA-AMMOS/aerie-ui/blob/develop/docs/ENVIRONMENT.md) in the PlanDev UI repository.
+See the [environment variables document](https://github.com/NASA-AMMOS/plandev-ui/blob/develop/docs/ENVIRONMENT.md) in the PlanDev UI repository.
 
 ## Hasura
 
diff --git a/deployment/README.md b/deployment/README.md
@@ -50,7 +50,7 @@ does not exceed the host's remaining available cores (considering other processe
 
 ## Starting the Services
 
-Download and unzip the latest [Deployment.zip](https://github.com/NASA-AMMOS/aerie/releases) file onto your local machine, then do:
+Download and unzip the latest [Deployment.zip](https://github.com/NASA-AMMOS/plandev/releases) file onto your local machine, then do:
 
 ```sh
 cd deployment
@@ -72,4 +72,4 @@ docker-compose down
 ## Troubleshooting
 
 - Make sure you are starting all the Docker containers in a clean environment. This means before starting the services make sure all containers are removed, all images are removed, and all volumes are removed.
-- If you are having trouble and cannot find the answer here, please contact someone from the PlanDev team via the [#mpsa-aerie-users](https://app.slack.com/client/T024LMMEZ/C0163E42UBF) Slack channel.
+- If you are having trouble and cannot find the answer here, please contact someone from the PlanDev team via the [#mpsa-plandev-users](https://app.slack.com/client/T024LMMEZ/C0163E42UBF) Slack channel.
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -51,9 +51,9 @@ The PlanDev project relies on the ability to effectively query the Git history.
 
 Please follow these instructions when submitting a Pull Request:
 
-1. Search [GitHub](https://github.com/NASA-AMMOS/aerie/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort.
+1. Search [GitHub](https://github.com/NASA-AMMOS/plandev/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort.
 1. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add. Discussing the design up front helps to ensure that we're ready to accept your work.
-1. Clone the [PlanDev repo](https://github.com/NASA-AMMOS/aerie).
+1. Clone the [PlanDev repo](https://github.com/NASA-AMMOS/plandev).
 1. Make your changes in a new git branch:
 
    ```sh
@@ -77,7 +77,7 @@ Please follow these instructions when submitting a Pull Request:
    git push origin my-fix-branch
    ```
 
-1. In GitHub, send a pull request to `aerie:develop`.
+1. In GitHub, send a pull request to `plandev:develop`.
 1. If we suggest changes then:
 
 - Make the required updates.
@@ -110,27 +110,27 @@ After your pull request is merged, you can safely delete your branch and pull th
 
 ## <a name="submit-pr"></a> Required Checks on PRs
 
-When you submit a PR, we use Github Workflows to automatically run a number of CI-type checks on it, all of which must pass before the PR can be merged. These vary slightly from one repo to another, but mostly consist of unit tests, as well as end-to-end (e2e) tests for the backend and frontend (`aerie` and `aerie-ui`) repos. If your PR adds new tests to our existing test suites, they will automatically be run & validated with your PR.
+When you submit a PR, we use Github Workflows to automatically run a number of CI-type checks on it, all of which must pass before the PR can be merged. These vary slightly from one repo to another, but mostly consist of unit tests, as well as end-to-end (e2e) tests for the backend and frontend (`plandev` and `plandev-ui`) repos. If your PR adds new tests to our existing test suites, they will automatically be run & validated with your PR.
 
 You can see the status of these checks at the bottom of the PR on Github - it should say "All checks have passed" if all is well. If it says "Some checks are not successful", you'll need to troubleshoot the cause of the failure before your PR can be accepted. Click "show all checks", then "details" to get detailed server logs from every step of the GH action that failed. Note that some of these runs may also have *files attached* to the run, which contain more detailed logs.
 
 If you can't determine the cause of the failure from logs alone, it may be helpful to try and reproduce the problem locally. You can see the commands run by the Required Check actions by looking in each repo under `.github/workflows` - each `yml` file in this folder contains the setup & commands necessary to run the check locally yourself.
 
 ## <a name="submit-pr"></a> Running E2E Tests with specific branches/images
 
-Both `aerie` and `aerie-ui` repos contain **end-to-end (E2E) tests** which depend on code from other PlanDev repos. Specifically:
-- The `aerie` backend e2e test suite, which tests a fully running PlanDev API, depends on `aerie-gateway` since it is part of the API
-- The `aerie-ui` e2e suite, which tests a full PlanDev UI + backend, depends on `aerie` and `aerie-gateway` code since it is a full stack test
+Both `plandev` and `plandev-ui` repos contain **end-to-end (E2E) tests** which depend on code from other PlanDev repos. Specifically:
+- The `plandev` backend e2e test suite, which tests a fully running PlanDev API, depends on `plandev-gateway` since it is part of the API
+- The `plandev-ui` e2e suite, which tests a full PlanDev UI + backend, depends on `plandev` and `plandev-gateway` code since it is a full stack test
 
 Sometimes a new feature requires code changes in *multiple repos simultaneously*, eg. a UI PR may add a new UI element that displays a new database field, but relies on a corresponding backend PR to add the new field. In this case, the UI PR's e2e tests will fail unless it has a way to *specify* which backend PR(s)/branches should be used for the e2e test.
 
 To handle this situation, follow these steps with your PRs:
-1. When you submit an `aerie` or `aerie-gateway` PR, if your PR contains code that *other PRs depend on*, add the GH label **"publish"** to the PR. This will cause an additional workflow to run which *publishes* the code in that branch to a docker image called eg. `pr-9999` for use by other PRs.
-2. When you submit an `aerie-ui` or `aerie` PR, if it *depends on other PR(s)* (aerie or gateway) for its tests to pass, edit the **body of your PR** to contain one or both of the following lines:
+1. When you submit a `plandev` or `plandev-gateway` PR, if your PR contains code that *other PRs depend on*, add the GH label **"publish"** to the PR. This will cause an additional workflow to run which *publishes* the code in that branch to a docker image called eg. `pr-9999` for use by other PRs.
+2. When you submit an `plandev-ui` or `plandev` PR, if it *depends on other PR(s)* (plandev or gateway) for its tests to pass, edit the **body of your PR** to contain one or both of the following lines:
 ```
 ___REQUIRES_AERIE_PR___="9999"
 ___REQUIRES_GATEWAY_PR___="9999"
 ```
-Replace "9999" with the **PR number(s)** of the relevant `aerie`/`gateway` PR(s). PRs to `aerie-ui` allow either/both of these fields, while `aerie` PRs only allow a `gateway` PR to be specified.
+Replace "9999" with the **PR number(s)** of the relevant `plandev`/`gateway` PR(s). PRs to `plandev-ui` allow either/both of these fields, while `plandev` PRs only allow a `gateway` PR to be specified.
 
-For example, see [this PR](https://github.com/NASA-AMMOS/aerie-ui/pull/1420) or [this PR](https://github.com/NASA-AMMOS/aerie-ui/pull/1492).
+For example, see [this PR](https://github.com/NASA-AMMOS/plandev-ui/pull/1420) or [this PR](https://github.com/NASA-AMMOS/plandev-ui/pull/1492).
diff --git a/docs/DEVELOPER.md b/docs/DEVELOPER.md
@@ -51,21 +51,21 @@ If you use [IntelliJ IDEA](https://www.jetbrains.com/idea/), you can import the
 [Clone](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) the PlanDev repository:
 
 ```shell
-git clone https://github.com/NASA-AMMOS/aerie.git
-cd aerie
+git clone https://github.com/NASA-AMMOS/plandev.git
+cd plandev
 ```
 
 ## Building
 
 ```sh
-cd aerie
+cd plandev
 ./gradlew assemble
 ```
 
 ## Testing
 
 ```sh
-cd aerie
+cd plandev
 ./gradlew test
 ```
 
@@ -74,7 +74,7 @@ cd aerie
 Use the following task to print a report of the dependencies that have updates available.
 
 ```sh
-cd aerie
+cd plandev
 ./gradlew dependencyUpdates
 ```
 
@@ -83,7 +83,7 @@ cd aerie
 To run the PlanDev services you need to first set the proper environment variables. First copy the template:
 
 ```sh
-cd aerie
+cd plandev
 cp .env.template .env
 ```
 
@@ -103,16 +103,16 @@ POSTGRES_USER=postgres
 The [docker-compose.yml](../docker-compose.yml) in the root directory deploys PlanDev locally, creating containers using the artifacts from the build step above.
 
 ```sh
-cd aerie
+cd plandev
 docker-compose up --build --detach
 ```
 
-Once PlanDev is started you can visit [http://localhost](http://localhost) to view the [PlanDev UI](https://github.com/NASA-AMMOS/aerie-ui). You can visit [http://localhost:8080](http://localhost:8080) to view the [Hasura Console](https://hasura.io/).
+Once PlanDev is started you can visit [http://localhost](http://localhost) to view the [PlanDev UI](https://github.com/NASA-AMMOS/plandev-ui). You can visit [http://localhost:8080](http://localhost:8080) to view the [Hasura Console](https://hasura.io/).
 
 ## Stop PlanDev
 
 ```sh
-cd aerie
+cd plandev
 docker compose down
 ```
 
diff --git a/docs/GOVERNANCE.md b/docs/GOVERNANCE.md
@@ -12,7 +12,7 @@ Anyone who has downloaded, deployed, or operated the PlanDev system to meet a sp
 
 ### Contributor
 
-Contributors include anyone that provides input to the project. This includes code, issues, documentation, graphics, designs, or anything else that tangibly improves the project. We encourage you to start contributing right away by joining our [Discussions](https://github.com/NASA-AMMOS/aerie/discussions) or submitting an [Issue](https://github.com/NASA-AMMOS/aerie/issues). 
+Contributors include anyone that provides input to the project. This includes code, issues, documentation, graphics, designs, or anything else that tangibly improves the project. We encourage you to start contributing right away by joining our [Discussions](https://github.com/NASA-AMMOS/plandev/discussions) or submitting an [Issue](https://github.com/NASA-AMMOS/plandev/issues). 
 
 ### Triager
 
@@ -61,8 +61,8 @@ A subset of the collaborators forms the Technical Steering Committee (TSC). The
 
 The TSC is primarily responsible for the PlanDev core and UI projects:
 
-- https://github.com/NASA-AMMOS/aerie
-- https://github.com/NASA-AMMOS/aerie-ui
+- https://github.com/NASA-AMMOS/plandev
+- https://github.com/NASA-AMMOS/plandev-ui
 
 However, the TSC also has responsibility over some projects, which are dependencies of the core projects:
 
diff --git a/docs/UPDATING_JNISPICE.MD b/docs/UPDATING_JNISPICE.MD
@@ -22,7 +22,7 @@ If you have already set up your machine for PlanDev development then all of thes
 
 This step has been entirely automated.
 
-1. Navigate to the ["Create x86 JNISpice Artifacts"](https://github.com/NASA-AMMOS/aerie/actions/workflows/create_jnispice.yml) Action on the PlanDev GitHub.
+1. Navigate to the ["Create x86 JNISpice Artifacts"](https://github.com/NASA-AMMOS/plandev/actions/workflows/create_jnispice.yml) Action on the PlanDev GitHub.
 2. Click "Run Workflow" and run the Workflow against `develop`.
 3. When the workflow has finished, navigate to the run's "Summary" page. Download everything under "Artifacts".
 4. Extract all the downloaded Artifacts.
diff --git a/gradle.properties b/gradle.properties
@@ -1,6 +1,6 @@
 # Properties for configuring the publish task.
 publishing.name=GitHubPackages
-publishing.url=https://maven.pkg.github.com/nasa-ammos/aerie
+publishing.url=https://maven.pkg.github.com/nasa-ammos/plandev
 publishing.usernameEnvironmentVariable=GITHUB_ACTOR
 publishing.passwordEnvironmentVariable=GITHUB_TOKEN
 
diff --git a/procedural/timeline/build.gradle b/procedural/timeline/build.gradle
@@ -60,7 +60,7 @@ dokkaHtmlPartial.configure {
       sourceLink {
         localDirectory.set(file("timeline/src/main/kotlin"))
         remoteUrl.set(new URL(
-            "https://github.com/NASA-AMMOS/aerie/blob/feat/java-timeline-library/timeline/src/main/kotlin/"
+            "https://github.com/NASA-AMMOS/plandev/blob/feat/java-timeline-library/timeline/src/main/kotlin/"
         ))
         remoteLineSuffix.set("#L")
       }
diff --git a/workspace-server/src/main/java/gov/nasa/jpl/aerie/workspace/server/FormattedError.java b/workspace-server/src/main/java/gov/nasa/jpl/aerie/workspace/server/FormattedError.java
@@ -25,7 +25,7 @@
 /**
  * Class for formatting exceptions thrown during in Workspaces into JSON objects
  * that meet the Aerie HTTP endpoint error message format
- * Relevant ticket going over said format: https://github.com/NASA-AMMOS/aerie/issues/1732
+ * Relevant ticket going over said format: https://github.com/NASA-AMMOS/plandev/issues/1732
  */
 @JsonSerialize(using = FormattedError.FormattedErrorSerializer.class)
 final class FormattedError {
