Remove automatic lockfile update workflow

.github/workflows/ci-python.yml

@@ -7,13 +7,13 @@ on:
       - compass/**
       - .github/workflows/ci-python.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   pull_request:
     paths:
       - compass/**
       - .github/workflows/ci-python.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   workflow_dispatch:
 
 jobs:
@@ -56,6 +56,7 @@ jobs:
         environments: pdev
 
     - run: |
+        pixi reinstall -e pdev --locked NREL-COMPASS
         pixi run -e pdev --locked tests-u
 
   unit-tests:

.github/workflows/ci-rust.yml → .github/workflows/ci-rust_code.yml

@@ -1,4 +1,4 @@
-name: Rust checks
+name: Rust Checks
 
 on:
   push:
@@ -12,21 +12,21 @@ on:
       - Cargo.lock
       - .github/workflows/ci-rust.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   pull_request:
     paths:
       - crates/**
       - Cargo.toml
       - Cargo.lock
       - .github/workflows/ci-rust.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   schedule:
     - cron: '0 5 * * 1'
 
 jobs:
   check:
-    name: Rust - Check
+    name: Rust - Cargo Check
     runs-on: ubuntu-latest
     steps:
       - name: Checkout sources
@@ -53,7 +53,7 @@ jobs:
   lints:
     # Only run tests if code looks OK
     needs: check
-    name: Rust - Lint
+    name: Rust - Clippy Lint
     runs-on: ubuntu-latest
     steps:
       - name: Checkout sources
@@ -84,7 +84,7 @@ jobs:
   test:
     # Only run tests if code looks OK
     needs: check
-    name: Rust - Test
+    name: Rust - Tests
     runs-on: ${{ matrix.os }}
     strategy:
       fail-fast: false
@@ -110,7 +110,7 @@ jobs:
       - run: pixi run -e rdev tests-r
 
   publish-dry:
-    name: Rust - Publish (dry-run)
+    name: Rust - Publishing (dry-run)
     # Only run tests if code looks OK
     needs: check
     runs-on: ubuntu-latest

.github/workflows/docs.yml

@@ -8,14 +8,14 @@ on:
       - compass/**
       - .github/workflows/docs.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   push:
     branches: [main]
     paths:
       - compass/**
       - .github/workflows/docs.yml
       - pyproject.toml
-      - "*.lock"
+      - pixi.lock
   release:
     types: [created, published]
   workflow_dispatch:

docs/source/dev/README.rst

@@ -377,10 +377,17 @@ When you are ready to release a new version of COMPASS, please follow these step
 5) Click on the "Select Tag" dropdown and type in a **new** tag. Be sure to follow `Semantic Versioning <https://semver.org/>`_. You may be prompted to create the new tag - make sure to do so
 6) Proofread the release notes and make any necessary adjustments
 7) Click "Publish Release"
-8) Once the release is published and the tag has been created, verify that a PR has been opened to update the pixi lockfile (you may have to wait some time for the GHA to run)
-9) Fill out any missing details in the PR (set yourself as the assignee, add any relevant project and milestone details, etc.)
-10) Request a review from another core COMPASS developer and merge the PR once approved
+8) Once the release is published and the tag has been created, you need to manually update the pixi lockfile:
+
+   a) Check out a new branch (e.g., ``update-lockfile-vX.Y.Z``)
+   b) Run ``pixi update nrel-compass`` to update the lockfile with the new COMPASS version
+   c) If needed, run ``pixi reinstall`` or ``pixi reinstall -e pdev`` to ensure the environment is consistent
+   d) Commit the updated ``pixi.lock`` file
+   e) Push your branch and open a PR with a title like "Update pixi lockfile for vX.Y.Z release"
+   f) Fill out any missing details in the PR (set yourself as the assignee, add any relevant project and milestone details, etc.)
+   g) Request a review from another core COMPASS developer and merge the PR once approved
 
 Congratulations, you have just released a new version of COMPASS!
+
 You may want to verify that the release has been published to `PyPi <https://pypi.org/project/NREL-COMPASS/>`_
 (if not, check the "Upload to PyPi" GitHub Action).