2026.01.000 #176

chrisb13 · 2026-01-07T22:33:01Z

New release with updates to all upstream components - as noted in ACCESS-NRI/access-om3-configs#1028 (comment)

🚀 The latest prerelease access-om3/pr176-17 at fb73b7c is here: #176 (comment) 🚀

see #174 ACCESS-NRI/access-om3-configs#1029

Co-authored-by: Anton Steketee <79179784+anton-seaice@users.noreply.github.com>

github-actions · 2026-01-07T22:33:39Z

The model version in the ./spack.yaml has not been updated.
You can update it manually.

github-actions · 2026-01-07T22:34:07Z

🚀 Attempted to deploy access-om3 Prerelease pr176-1 with commit 6c9717f

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-07T23:29:27Z

🚀 Attempted to deploy access-om3 Prerelease pr176-1 with commit 6c9717f

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.08.003
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice

Updating openmpi as suggested by @anton-seaice ACCESS-NRI/access-om3-configs#1028 (comment) / @helenmacdonald

github-actions · 2026-01-10T02:56:24Z

🚀 Attempted to deploy access-om3 Prerelease pr176-2 with commit 9ca959c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.08.003
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

ACCESS-NRI/ACCESS-OM3#176 (comment) Testing `openmpi` version '@5.0.8'

anton-seaice · 2026-01-11T23:47:06Z

Should be faster now @chrisb13, it's found the already built esmf :

[+] covllzb ^esmf@8.7.0%oneapi@2025.2.0 cflags='-mtune=sapphirerapids -unroll -march=sapphirerapids' cxxflags='-mtune=sapphirerapids -march=sapphirerapids -unroll' fflags='-mtune=sapphirerapids -march=sapphirerapids -unroll' ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf+shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-rocky8-x86_64_v4

It re-uses '`covllzb' for builds in this PR (note that hash only exists in this PR) - to do this in a different PR use the hash from an esmf build in that PR.

github-actions · 2026-01-12T00:06:00Z

🚀 Attempted to deploy access-om3 Prerelease pr176-3 with commit 7e87079

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2025.08.003
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

@chrisb13

@chrisb13 and @helenmacdonald updating `ACCESS-NRI/GFDL-generic-tracers` as determined [here](ACCESS-NRI/access-om3-configs#1028 (comment))

Test to see if GitHub will run two deployments at once?

github-actions · 2026-01-12T00:12:01Z

🚀 Attempted to deploy access-om3 Prerelease pr176-4 with commit 4726d44

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-12T00:15:15Z

🚀 Attempted to deploy access-om3 Prerelease pr176-5 with commit b683a8f

🖥️ `Gadi` Deployment ❌

Needed to update acccess-spack-packages to a newer version to accommodate generic-tracers `2025.09.000` (this build failed https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/20904149711/job/60054678559)

chrisb13 · 2026-01-12T00:32:35Z

Should be faster now @chrisb13

Thanks @anton-seaice, I think it's now faster, about ~30 minutes (even with just your change). Is that expected?

anton-seaice · 2026-01-12T00:37:47Z

I think it's now faster, about ~30 minutes (even with just your change). Is that expected?

Sounds plausible - depends how far down the dependency chain the change is. e.g. if the only change is to access3 (which has no dependents) then its fast, if the change is to openmpi then its very slow (which has many dependents)

chrisb13 · 2026-01-12T00:40:33Z

Ok but with your recent change, which only changed the source for esmf isn't it effectively no change? As in, everything is already built so is it taking 30 minutes to basically determine that nothing is needed?

github-actions · 2026-01-13T05:06:11Z

🚀 Attempted to deploy access-om3 Prerelease pr176-9 with commit 35d8ebf

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-13T05:07:01Z

🚀 Attempted to deploy access-om3 Prerelease pr176-10 with commit 6609917

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-13T05:26:43Z

🚀 Attempted to deploy access-om3 Prerelease pr176-11 with commit 39b3657

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-11

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-11 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

Rolling back mom6 version for the time being whilst we check that the latest `access3-share` works (`rc-2026.01.000`). This uses the forks version of CMEPS, CDEPS and CESM_share as well as the updated patches/files from here: ACCESS-NRI/access3-share#22 (comment) Also related: ACCESS-NRI/access3-share#19

github-actions · 2026-01-19T04:58:31Z

🚀 Attempted to deploy access-om3 Prerelease pr176-12 with commit d84ae63

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-12

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-12 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

Looking to test the theory that the `access3-share` update broke historical repro, see: ACCESS-NRI/access-om3-configs#1033 (comment)

github-actions · 2026-01-19T21:58:04Z

🚀 Attempted to deploy access-om3 Prerelease pr176-13 with commit eb8627e

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-13

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-13 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

Changing version of `access3-share` incrementally across the components. This is just testing the change of CMEPS to using our fork. See: - ACCESS-NRI/access3-share@342685c - ACCESS-NRI/access3-share#19

Changing version of `access3-share` incrementally across the components. This is just testing the change of CMEPS _and_ CESM_share (with access changes applied). See: - #176 - ACCESS-NRI/access3-share@3b44248 - ACCESS-NRI/access3-share@342685c

github-actions · 2026-01-21T22:34:58Z

🚀 Attempted to deploy access-om3 Prerelease pr176-14 with commit e01c4ce

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-21T22:39:39Z

🚀 Attempted to deploy access-om3 Prerelease pr176-15 with commit 705468c

🖥️ `Gadi` Deployment ❌

Based on this comment: ACCESS-NRI/access3-share#22 (comment) Anton has done a force push of the branch `rc-2026.01.000`, and comments (see above link) that each commit builds. Seeing if it also builds in om3 (could attempt a repro test if applicable). This commit tests: "Update the CESM_share 1.1.18" [dcbe86b](ACCESS-NRI/access3-share@dcbe86b)

Based on this comment: ACCESS-NRI/access3-share#22 (comment) Anton has done a force push of the branch `rc-2026.01.000`, and comments (see above link) that each commit builds. Seeing if it also builds in om3 (could attempt a repro test if applicable). This commit tests: "Update to CDEPS 1.0.86" [4daf043](ACCESS-NRI/access3-share@4daf043)

Based on this comment: ACCESS-NRI/access3-share#22 (comment) Anton has done a force push of the branch `rc-2026.01.000`, and comments (see above link) that each commit builds. Seeing if it also builds in om3 (could attempt a repro test if applicable). This commit tests: "Update to CMEPS 1.1.31" [ed7680e](ACCESS-NRI/access3-share@ed7680e)

github-actions · 2026-01-22T01:13:06Z

🚀 Attempted to deploy access-om3 Prerelease pr176-18 with commit 36d0803

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-18

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-18 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

github-actions · 2026-01-22T01:13:19Z

🚀 Attempted to deploy access-om3 Prerelease pr176-16 with commit 443d40e

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-16

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-16 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

Testing: ACCESS-NRI/ACCESS-OM3#176 (comment) i.e. "Update the CESM_share 1.1.18" [dcbe86b](ACCESS-NRI/access3-share@dcbe86b)

github-actions · 2026-01-22T01:26:33Z

🚀 Attempted to deploy access-om3 Prerelease pr176-17 with commit fb73b7c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

2025.08.001 as a Release (when merged).
pr176-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr176-17

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr176-17 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

access-nri/spack on branch 0.22
access-nri/spack-packages version 2026.01.000
access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

Testing: ACCESS-NRI/ACCESS-OM3#176 (comment) i.e. "Update to CDEPS 1.0.86" [4daf043](ACCESS-NRI/access3-share@4daf043)

Testing: ACCESS-NRI/ACCESS-OM3#176 (comment) i.e. "Update to CMEPS 1.1.31" [ed7680e](ACCESS-NRI/access3-share@ed7680e) (we expect this to fail, it'll be weird if it doesn't!)

chrisb13 and others added 2 commits January 7, 2026 12:23

Update comments in spack.yaml for clarity

7e2fc7d

see #174 ACCESS-NRI/access-om3-configs#1029

Update spack.yaml

6c9717f

Co-authored-by: Anton Steketee <79179784+anton-seaice@users.noreply.github.com>

chrisb13 requested a review from a team as a code owner January 7, 2026 22:33

anton-seaice marked this pull request as draft January 7, 2026 22:34

anton-seaice removed the request for review from a team January 7, 2026 22:35

chrisb13 mentioned this pull request Jan 7, 2026

Update comments in spack.yaml for clarity #175

Closed

anton-seaice temporarily deployed to Gadi Prerelease January 7, 2026 22:35 — with GitHub Actions Inactive

Update spack.yaml

9ca959c

Updating openmpi as suggested by @anton-seaice ACCESS-NRI/access-om3-configs#1028 (comment) / @helenmacdonald

chrisb13 temporarily deployed to Gadi Prerelease January 10, 2026 01:41 — with GitHub Actions Inactive

chrisb13 added a commit to ACCESS-NRI/access-om3-configs that referenced this pull request Jan 10, 2026

Update Payu configuration for module paths

92f0834

ACCESS-NRI/ACCESS-OM3#176 (comment) Testing `openmpi` version '@5.0.8'

chrisb13 mentioned this pull request Jan 10, 2026

Testing model build 2026.01.000 on dev-MC_100km_jra_ryf ACCESS-NRI/access-om3-configs#1033

Draft

Update spack.yaml

7e87079

anton-seaice temporarily deployed to Gadi Prerelease January 11, 2026 23:35 — with GitHub Actions Inactive

Update spack.yaml

4726d44

@chrisb13 and @helenmacdonald updating `ACCESS-NRI/GFDL-generic-tracers` as determined [here](ACCESS-NRI/access-om3-configs#1028 (comment))

chrisb13 had a problem deploying to Gadi Prerelease January 12, 2026 00:07 — with GitHub Actions Failure

Update spack.yaml

b683a8f

Test to see if GitHub will run two deployments at once?

chrisb13 had a problem deploying to Gadi Prerelease January 12, 2026 00:11 — with GitHub Actions Failure

Update spack-packages version to 2025.12.000

7160dae

Needed to update acccess-spack-packages to a newer version to accommodate generic-tracers `2025.09.000` (this build failed https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/20904149711/job/60054678559)

chrisb13 temporarily deployed to Gadi Prerelease January 12, 2026 00:20 — with GitHub Actions Inactive

This was referenced Jan 16, 2026

RC for access-om3 new upstream build: 2026.01.000 ACCESS-NRI/CMEPS#11

Closed

RC for access-om3 new upstream build: 2026.01.000 ACCESS-NRI/CDEPS#1

Closed

chrisb13 temporarily deployed to Gadi Prerelease January 19, 2026 04:33 — with GitHub Actions Inactive

Update access3 package version in spack.yaml

eb8627e

Looking to test the theory that the `access3-share` update broke historical repro, see: ACCESS-NRI/access-om3-configs#1033 (comment)

chrisb13 temporarily deployed to Gadi Prerelease January 19, 2026 21:33 — with GitHub Actions Inactive

Update spack.yaml

e01c4ce

Changing version of `access3-share` incrementally across the components. This is just testing the change of CMEPS to using our fork. See: - ACCESS-NRI/access3-share@342685c - ACCESS-NRI/access3-share#19

chrisb13 had a problem deploying to Gadi Prerelease January 21, 2026 22:25 — with GitHub Actions Failure

Update spack.yaml

705468c

Changing version of `access3-share` incrementally across the components. This is just testing the change of CMEPS _and_ CESM_share (with access changes applied). See: - #176 - ACCESS-NRI/access3-share@3b44248 - ACCESS-NRI/access3-share@342685c

chrisb13 had a problem deploying to Gadi Prerelease January 21, 2026 22:32 — with GitHub Actions Failure

chrisb13 mentioned this pull request Jan 21, 2026

Migrate from patches to forks on CDEPS, CMEPS, cesm_share ACCESS-NRI/access3-share#22

Open

chrisb13 temporarily deployed to Gadi Prerelease January 22, 2026 00:44 — with GitHub Actions Inactive

chrisb13 temporarily deployed to Gadi Prerelease January 22, 2026 00:46 — with GitHub Actions Inactive

chrisb13 temporarily deployed to Gadi Prerelease January 22, 2026 00:47 — with GitHub Actions Inactive

chrisb13 added a commit to ACCESS-NRI/access-om3-configs that referenced this pull request Jan 22, 2026

Update config.yaml

9bc9044

Testing: ACCESS-NRI/ACCESS-OM3#176 (comment) i.e. "Update the CESM_share 1.1.18" [dcbe86b](ACCESS-NRI/access3-share@dcbe86b)

chrisb13 added a commit to ACCESS-NRI/access-om3-configs that referenced this pull request Jan 22, 2026

Update config.yaml

cd85b2a

Testing: ACCESS-NRI/ACCESS-OM3#176 (comment) i.e. "Update to CDEPS 1.0.86" [4daf043](ACCESS-NRI/access3-share@4daf043)

2026.01.000 #176

Are you sure you want to change the base?

2026.01.000 #176

Uh oh!

Conversation

chrisb13 commented Jan 7, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Jan 7, 2026

Uh oh!

github-actions bot commented Jan 7, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 7, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 10, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Jan 11, 2026

Uh oh!

github-actions bot commented Jan 12, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 12, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 12, 2026

🖥️ Gadi Deployment ❌

Uh oh!

chrisb13 commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anton-seaice commented Jan 12, 2026

Uh oh!

chrisb13 commented Jan 12, 2026

Uh oh!

github-actions bot commented Jan 13, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 13, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 13, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 19, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 19, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 21, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 21, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 22, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 22, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 22, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

chrisb13 commented Jan 7, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

chrisb13 commented Jan 12, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️