Merge branch 'main' into copilot/fix-2877

Author: IsabelParedes

.github/copilot-instructions.md

@@ -3,34 +3,21 @@
 Emscripten-forge is a conda package repository for building packages targeting the `emscripten-wasm32` platform (WebAssembly). The repository contains package recipes and uses `pixi` for environment management and `rattler-build` for package building.
 
 
-### Repository Structure
-```
-recipes/
-├── recipes/
-├── recipes_emscripten/ # this is where the recipes need to go
-...
-```
-
-### Key Directories and Files
-- `recipes/recipes_emscripten/` - All WebAssembly package recipes (283+ packages)
-
+## Add New Recipes
 
-### Package Types and Examples
-The repository supports multiple package types:
+To add new recipes follow the following steps:
 
-**Python packages**: zarr, numpy, scipy, matplotlib, pandas, etc.
-- Use `cross-python_${{ target_platform }}` build requirement
-- Example: `recipes/recipes_emscripten/zarr/`
+* check if the recipe needs building or is a noarch recipes. We **do not add noarch recipes**
+* check if the recipe is already present in the repository. If it is, update the existing recipe as needed.
+* if not, create a new directory for the recipe under `recipes/recipes_emscripten/`
+* add a `recipe.yaml` and file with the necessary metadata and build instructions
+* add a `build.sh` script to handle the build process if its more than a one-liner
+* include any additional files (e.g., patches, scripts) as needed
+* test the recipe using the appropriate testing framework
 
-**C/C++ packages**: boost-cpp, arrow-cpp, opencv, etc.  
-- Use `emcmake` instead of `cmake`, `emmake` instead of `make`
-- Example: `recipes/recipes_emscripten/boost-cpp/`
 
-**Rust packages**: cryptography, pydantic-core, etc.
-- Use `maturin` for PyO3 packages
-- Pin `cffi == 1.15.1` during transition period
 
-### Testing
+### Recipe test section
 For python packages, tests are defined in recipe.yaml files:
 ```yaml
 tests:
@@ -40,4 +27,39 @@ tests:
     - test_import_[package].py
 ```
 
-For python packages, most tests are simple import tests. Tests run automatically during package builds.
+For python packages, most tests are simple import tests. These tests run automatically during package builds. 
+
+For non-python packages, its enough to check if the expected files exist.
+For a header only library this might look like:
+
+```yaml
+tests:
+  - script:
+    - if: unix or emscripten
+      then:
+        - test -d ${PREFIX}/include/xtensor
+        - test -f ${PREFIX}/include/xtensor/xarray.hpp
+        - test -f ${PREFIX}/share/cmake/xtensor/xtensorConfig.cmake
+        - test -f ${PREFIX}/share/cmake/xtensor/xtensorConfigVersion.cmake
+```
+
+## Check if the recipe is working
+
+to build the recipe you worked on with rattler-build with:
+(where YOUR_RECIPE_NAME is the name of the directory you created):
+
+
+  rattler-build build \
+  --package-format tar-bz2 \
+  -c https://repo.prefix.dev/emscripten-forge-dev \
+  -c microsoft \
+  -c conda-forge \
+  --target-platform emscripten-wasm32 \
+  --skip-existing none \
+  -m variant.yaml \
+  --recipe recipes/recipes_emscripten/YOUR_RECIPE_NAME
+
+
+* this will build the recipe and run tests 
+* check the output for any errors or warnings and try to resolve them
+* if you fail to run these commands report so

.github/workflows/copilot-setup-steps.yml

@@ -0,0 +1,33 @@
+name: "Copilot Setup Steps"
+
+# Automatically run the setup steps when they are changed to allow for easy validation, and
+# allow manual testing through the repository's "Actions" tab
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+  pull_request:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+
+jobs:
+  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
+  copilot-setup-steps:
+    runs-on: ubuntu-latest
+
+    # Set the permissions to the lowest permissions possible needed for your steps.
+    # Copilot will be given its own token for its operations.
+    permissions:
+      # If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
+      contents: read
+
+    # You can define any steps you want, and they will run before the agent starts.
+    # If you do not check out your code, Copilot will do this for you.
+    steps:
+
+      - name: Checkout repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: prefix-dev/setup-pixi@v0.9.0