From 146a6a2ca9b217908bb49d7b5bb629094aa01316 Mon Sep 17 00:00:00 2001
From: pfebrer <42074085+pfebrer@users.noreply.github.com>
Date: Sat, 14 Oct 2023 10:54:03 +0200
Subject: [PATCH] Update DEPLOY.md with pyodide instructions

---
 DEPLOY.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/DEPLOY.md b/DEPLOY.md
index f6e160c432..622a0f3242 100644
--- a/DEPLOY.md
+++ b/DEPLOY.md
@@ -61,3 +61,18 @@ The release cycle should be performed like this:
    3. Propose merge-request.
    4. Check CI succeeds.
    5. Accept merge and the new version will be uploaded.
+
+8. Update pyodide version
+
+   Until web assembly (wasm) wheels are supported by PyPi, they
+   are managed directly in the pyodide repository. The update steps
+   are very similar to conda, except all packages are managed
+   in a single repository. The meta.yaml is at packages/sisl/meta.yaml.
+   Follow these steps:
+
+   1. branch off https://github.com/pyodide/pyodide
+   2. Edit packages/sisl/meta.yaml by updating version, source url and sha256
+   3. Propose merge-request.
+   4. Check CI succeeds. If it doesn't you can test locally by following
+      instructions [here](https://pyodide.org/en/stable/development/new-packages.html#building-a-python-package-in-tree)
+   5. Wait for the pyodide team to accept your request.