Limit number of CI configs

Author: Bromeon

.github/other/check-example.sh

@@ -23,6 +23,7 @@ fi
 PRE="# EXAMPLE $example |"
 dir="examples/$example/godot"
 logfile="stderr-$example.log"
+# stdout also outputs some "ERROR:" messages, these are currently ignored.
 
 # In .gdextension file, use paths to release artifacts.
 sed -i'.bak' "s!/debug/!/release/!g" "$dir/rust.gdextension"

.github/workflows/ci.yml

@@ -165,13 +165,6 @@ jobs:
             artifact-name: windows-nightly
             godot-binary: godot.windows.editor.dev.x86_64.exe
 
-          # On Windows (only), test double precision.
-          - name: windows-double
-            os: windows-latest
-            artifact-name: windows-double-nightly
-            godot-binary: godot.windows.editor.dev.double.x86_64.exe
-            rust-extra-args: --features godot/api-custom,godot/double-precision
-
           # Linux
 
           - name: linux
@@ -188,15 +181,21 @@ jobs:
             os: ubuntu-22.04
             artifact-name: linux-4.2
             godot-binary: godot.linuxbsd.editor.dev.x86_64
+            rust-extra-args: --features godot/api-4.2
 
           - name: linux-4.1
             os: ubuntu-22.04
             artifact-name: linux-4.1
             godot-binary: godot.linuxbsd.editor.dev.x86_64
+            rust-extra-args: --features godot/api-4.1
 
           # Do not run memchecks; increases CI complexity too much with the patching and everything.
           # Such cases need to be tested in the itest suite in the main repo.
 
+          # Also don't test double precision. Makes a lot of code more difficult to write (real conversions etc), missing
+          # the point of examples being approachable. Users who need it are trusted to adjust code based on compile errors.
+
+
     steps:
       - uses: actions/checkout@v4