From 98abe06e26f74c19f5eb8cad6357c7dd8705c97d Mon Sep 17 00:00:00 2001
From: Tristan ALLAIRE <tristan.allaire@alarch.fr>
Date: Fri, 15 Mar 2024 12:11:11 +0100
Subject: [PATCH] CI pipeline updated

---
 .ci/.gitlab-ci-changelog.yml                  |  2 +-
 .ci/.gitlab-ci-notify.yml                     |  4 +-
 .ci/.gitlab-ci-release.yml                    | 18 +++---
 .ci/scripts/AUR/template/template.PKGBUILD    |  2 +-
 .../homebrew/template/homebrew-template.rb    |  4 +-
 .../nix/update_ligo_default_nix_file.sh       |  2 +-
 ...te_distribution_references_with_release.sh |  6 +-
 HomebrewFormula/ligo.rb                       |  4 +-
 HomebrewFormula/ligo@0.63.2.rb                |  4 +-
 HomebrewFormula/ligo@0.66.0.rb                |  4 +-
 HomebrewFormula/ligo@0.67.1.rb                |  4 +-
 HomebrewFormula/ligo@0.68.0.rb                |  4 +-
 HomebrewFormula/ligo@0.69.0.rb                |  4 +-
 HomebrewFormula/ligo@0.70.0.rb                |  4 +-
 HomebrewFormula/ligo@0.70.1.rb                |  4 +-
 HomebrewFormula/ligo@0.71.0.rb                |  4 +-
 HomebrewFormula/ligo@0.71.1.rb                |  4 +-
 HomebrewFormula/ligo@0.72.0.rb                |  4 +-
 HomebrewFormula/ligo@0.73.0.rb                |  4 +-
 HomebrewFormula/ligo@1.0.0.rb                 |  4 +-
 HomebrewFormula/ligo@1.1.0.rb                 |  4 +-
 HomebrewFormula/ligo@1.2.0.rb                 |  4 +-
 HomebrewFormula/ligo@1.3.0.rb                 |  4 +-
 HomebrewFormula/ligo@1.4.0.rb                 |  4 +-
 changelog/1722                                |  2 +-
 changelog/1937                                |  2 +-
 changelog/1950                                |  4 +-
 changelog/1974                                |  2 +-
 changelog/2038                                |  2 +-
 changelog/2223                                |  2 +-
 changelog/2393                                |  2 +-
 changelog/2503                                |  2 +-
 changelog/2993                                |  2 +-
 changelog/3031                                |  2 +-
 .../documentation-and-releases.md             |  2 +-
 .../docs/contributors/ligo_test_guide.md      | 16 ++---
 gitlab-pages/docs/demo/ligo-snippet.md        |  2 +-
 gitlab-pages/docs/faq/v1-migration-guide.md   | 60 +++++++++----------
 gitlab-pages/docs/intro/editor-support.md     |  4 +-
 gitlab-pages/docs/intro/installation.md       | 28 ++++-----
 gitlab-pages/docs/intro/ligo-intro.md         |  2 +-
 gitlab-pages/docs/language-basics/types.md    |  2 +-
 .../inter-contract-calls.md                   |  2 +-
 gitlab-pages/website/docusaurus.config.js     |  4 +-
 .../src/components/Community/index.tsx        |  2 +-
 .../website/src/components/News/index.tsx     |  2 +-
 .../website/src/theme/Footer/Layout/index.js  |  2 +-
 .../documentation-and-releases.md             |  2 +-
 .../contributors/ligo_test_guide.md           | 16 ++---
 .../version-1.2.0/demo/ligo-snippet.md        |  2 +-
 .../version-1.2.0/faq/v1-migration-guide.md   | 60 +++++++++----------
 .../version-1.2.0/intro/editor-support.md     |  4 +-
 .../version-1.2.0/intro/installation.md       | 28 ++++-----
 .../version-1.2.0/intro/ligo-intro.md         |  2 +-
 .../version-1.2.0/language-basics/types.md    |  2 +-
 .../version-1.2.0/reference/toplevel.md       |  4 +-
 .../inter-contract-calls.md                   |  2 +-
 .../documentation-and-releases.md             |  2 +-
 .../contributors/ligo_test_guide.md           | 16 ++---
 .../version-1.3.0/demo/ligo-snippet.md        |  2 +-
 .../version-1.3.0/faq/v1-migration-guide.md   | 60 +++++++++----------
 .../version-1.3.0/intro/editor-support.md     |  4 +-
 .../version-1.3.0/intro/installation.md       | 28 ++++-----
 .../version-1.3.0/intro/ligo-intro.md         |  2 +-
 .../version-1.3.0/language-basics/types.md    |  2 +-
 .../version-1.3.0/reference/toplevel.md       |  4 +-
 .../inter-contract-calls.md                   |  2 +-
 .../documentation-and-releases.md             |  2 +-
 .../contributors/ligo_test_guide.md           | 16 ++---
 .../version-1.4.0/demo/ligo-snippet.md        |  2 +-
 .../version-1.4.0/faq/v1-migration-guide.md   | 60 +++++++++----------
 .../version-1.4.0/intro/editor-support.md     |  4 +-
 .../version-1.4.0/intro/installation.md       | 28 ++++-----
 .../version-1.4.0/intro/ligo-intro.md         |  2 +-
 .../version-1.4.0/language-basics/types.md    |  2 +-
 .../inter-contract-calls.md                   |  2 +-
 scripts/build_docker_image.sh                 |  2 +-
 scripts/changelog.md.mustache                 | 48 +++++++--------
 scripts/changelog.txt.mustache                | 26 ++++----
 scripts/distribution/generic/env_variables.sh |  2 +-
 scripts/install_build_environment.sh          |  2 +-
 scripts/installer.sh                          |  6 +-
 scripts/ligo_ci.sh                            |  2 +-
 scripts/list-to-dos.sh                        |  4 +-
 scripts/release-notes.md.mustache             | 20 +++----
 scripts/release-notes.txt.mustache            | 20 +++----
 src/bin/expect_tests/contract_tests.ml        |  2 +-
 src/bin/expect_tests/get_scope.ml             |  2 +-
 .../expect_tests/ligo_interpreter_tests.ml    |  8 +--
 src/bin/repl.ml                               |  2 +-
 src/main/analytics/analytics.ml               |  2 +-
 .../shared/repository_url.ml                  |  4 +-
 .../passes/pattern_restriction.ml             |  2 +-
 src/passes/14-spilling/compiler.ml            |  2 +-
 src/test/contracts/balance_constant.jsligo    |  2 +-
 src/test/contracts/balance_constant.mligo     |  2 +-
 src/test/contracts/let_multiple.mligo         |  6 +-
 .../Makefile                                  |  2 +-
 .../Makefile                                  |  2 +-
 .../Makefile                                  |  2 +-
 .../core/Makefile                             |  2 +-
 .../float/Makefile                            |  2 +-
 .../rational/Makefile                         |  2 +-
 .../Makefile                                  |  2 +-
 .../core/Makefile                             |  2 +-
 .../float/Makefile                            |  2 +-
 .../rational/Makefile                         |  2 +-
 .../contracts/positive/let_in_recursive.mligo |  2 +-
 .../cameligo/original/2let_multiple.mligo     |  6 +-
 .../jsligo/original/4balance_constant.jsligo  |  2 +-
 src/test/transpilation/all_the_things.mligo   |  8 +--
 .../expected/all_the_things.mligo.expected    |  8 +--
 tools/debugger/docs/ligo-versions.md          |  2 +-
 .../src/Language/LIGO/Debugger/CLI/Types.hs   |  2 +-
 .../ligo-debugger/test/Test/LigoCall.hs       |  2 +-
 tools/emacs/ligo-mode.el                      |  2 +-
 tools/ligo-snippets/README.md                 |  4 +-
 tools/ligo-snippets/package-lock.json         |  2 +-
 tools/ligo-snippets/package.json              |  2 +-
 tools/vscode/README.md                        |  4 +-
 .../client/src/common/LigoProtocolClient.ts   |  2 +-
 tools/vscode/client/src/lsp/updateLigo.ts     |  8 +--
 tools/vscode/package.json                     |  6 +-
 tools/webide-new/flake.nix                    |  2 +-
 .../webide-new/ligo-webide-backend/Dockerfile |  2 +-
 .../ligo-webide-backend/src/Ligo.hs           |  2 +-
 .../webide-new/ligo-webide-frontend/README.md |  2 +-
 vendored-dune/GetoptLib/GetoptLib.opam        |  2 +-
 .../proto-alpha-utils/proto-alpha-utils.opam  |  4 +-
 .../proto-pre-alpha-utils.opam                |  4 +-
 .../simple-utils/simple-utils-js.opam         |  4 +-
 .../simple-utils/simple-utils-unix.opam       |  4 +-
 .../ligo-utils/simple-utils/simple-utils.opam |  4 +-
 .../ligo-utils/tezos-utils/tezos-utils.opam   |  4 +-
 vendored-dune/syntax-highlighting/Emacs.ml    |  2 +-
 .../SyntaxHighlighting.opam                   |  4 +-
 136 files changed, 453 insertions(+), 453 deletions(-)

diff --git a/.ci/.gitlab-ci-changelog.yml b/.ci/.gitlab-ci-changelog.yml
index 78a158c15a..fb6c876db1 100644
--- a/.ci/.gitlab-ci-changelog.yml
+++ b/.ci/.gitlab-ci-changelog.yml
@@ -18,7 +18,7 @@ add-changelog-entry:
       if [[ $exit_code != 0 ]]; then
         exit $exit_code
       fi
-    - git remote rm origin && git remote add origin "git@gitlab.com:ligolang/ligo.git" 
+    - git remote rm origin && git remote add origin "git@gitlab.com:mavryk-network/ligo.git" 
     - git add changelog/* changelog-tools/*
     - git commit -m "[Bot] add changelog entry"
     - git push origin HEAD:$CI_COMMIT_REF_NAME
diff --git a/.ci/.gitlab-ci-notify.yml b/.ci/.gitlab-ci-notify.yml
index a18e7abe04..1ebd90489d 100644
--- a/.ci/.gitlab-ci-notify.yml
+++ b/.ci/.gitlab-ci-notify.yml
@@ -1,14 +1,14 @@
 notify-christian-on-frontend-change:
   stage: post-build-action
   script:
-    - MESSAGE="Someone edited frontend https://gitlab.com/ligolang/ligo/-/merge_requests/$CI_MERGE_REQUEST_IID"
+    - MESSAGE="Someone edited frontend https://gitlab.com/mavryk-network/ligo/-/merge_requests/$CI_MERGE_REQUEST_IID"
     - "curl -d \"text=${MESSAGE}\" -d 'channel=UC5125SQP' -H \"Authorization: Bearer ${SLACK_LIGO_ALERTER_TOKEN}\" -X POST https://slack.com/api/chat.postMessage --trace-ascii /dev/stdout"
   when: on_failure
   rules:
   # 2654428 & UC5125SQP = Christian 
   - if: $GITLAB_USER_ID == "2654428"
     when: never
-  - if: '$CI_PIPELINE_SOURCE == "merge_request_event" && $CI_PROJECT_PATH == "ligolang/ligo"'
+  - if: '$CI_PIPELINE_SOURCE == "merge_request_event" && $CI_PROJECT_PATH == "mavryk-network/ligo"'
     changes:
       - src/stages/1-cst/**/*
       - src/passes/00-preprocessing/**/*
diff --git a/.ci/.gitlab-ci-release.yml b/.ci/.gitlab-ci-release.yml
index 1f0507ee87..d000e935fa 100644
--- a/.ci/.gitlab-ci-release.yml
+++ b/.ci/.gitlab-ci-release.yml
@@ -63,7 +63,7 @@ build_release_env_vars:
 create-tag:
   stage: release    
   script:
-    - git remote rm origin && git remote add origin "git@gitlab.com:ligolang/ligo.git"
+    - git remote rm origin && git remote add origin "git@gitlab.com:mavryk-network/ligo.git"
     # Don't want to tag for testing
     - echo $DRY_RUN_RELEASE
     - |
@@ -136,7 +136,7 @@ docker-m1:
     - docker image rm -f "${LIGO_IMAGE_TAG}-builder" >/dev/null 2>&1 || true
     - docker image rm -f "${LIGO_IMAGE_TAG}" >/dev/null 2>&1 || true
   rules:
-    - if: '$CI_COMMIT_TAG =~ /[0-9]+\.[0-9]+\.[0-9]/ && $CI_PROJECT_PATH == "ligolang/ligo"'
+    - if: '$CI_COMMIT_TAG =~ /[0-9]+\.[0-9]+\.[0-9]/ && $CI_PROJECT_PATH == "mavryk-network/ligo"'
       when: always
   artifacts:
     paths:
@@ -192,11 +192,11 @@ create_docker_stable_version:
     - job: determine_new_stable_version
       artifacts: true
   script:
-    - docker pull ligolang/ligo:$STABLE_VERSION
+    - docker pull mavrykdynamics/ligo:$STABLE_VERSION
     - |
       if [[ $DRY_RUN_RELEASE == "" ]]; then
-        docker tag ligolang/ligo:$STABLE_VERSION ligolang/ligo:stable
-        docker push ligolang/ligo:stable
+        docker tag mavrykdynamics/ligo:$STABLE_VERSION mavrykdynamics/ligo:stable
+        docker push mavrykdynamics/ligo:stable
       fi
 
 update_release_metadata:
@@ -234,7 +234,7 @@ update_release_metadata:
       if [[ $DRY_RUN_RELEASE != "" ]]; then
         CI_COMMIT_TAG=${CI_COMMIT_BRANCH#"release/"}
       fi
-    - git remote rm origin && git remote add origin "git@gitlab.com:ligolang/ligo.git"
+    - git remote rm origin && git remote add origin "git@gitlab.com:mavryk-network/ligo.git"
     - git fetch
     - git checkout release/$CI_COMMIT_TAG
     - ./.ci/scripts/release_metadata/edit_release_metadata.sh LAST_RELEASE_VERSION $CI_COMMIT_TAG
@@ -372,7 +372,7 @@ update-ligo-bin-PKGBUILD:
   stage: pretooling
   script:
     - LAST_TAG_JOB_ID=`./.ci/scripts/release_metadata/read_release_metadata.sh LAST_TAG_JOB_ID`
-    - ./.ci/scripts/AUR/create_new_pkgbuild_version.sh https://gitlab.com/ligolang/ligo/-/jobs/$LAST_TAG_JOB_ID/artifacts/raw/ligo.deb $RELEASE_VERSION
+    - ./.ci/scripts/AUR/create_new_pkgbuild_version.sh https://gitlab.com/mavryk-network/ligo/-/jobs/$LAST_TAG_JOB_ID/artifacts/raw/ligo.deb $RELEASE_VERSION
     - cp ./.ci/scripts/AUR/ligo.PKGBUILD ./ligo-bin/PKGBUILD
   needs:
     - job: initialize-aur-repo
@@ -417,7 +417,7 @@ calculate_nix_SRI:
       when: always
   script: 
     - LAST_TAG_JOB_ID=`./.ci/scripts/release_metadata/read_release_metadata.sh LAST_TAG_JOB_ID`
-    - BINARY_GITLAB_ARTIFACT_URL="https://gitlab.com/ligolang/ligo/-/jobs/$LAST_TAG_JOB_ID/artifacts/raw/ligo"
+    - BINARY_GITLAB_ARTIFACT_URL="https://gitlab.com/mavryk-network/ligo/-/jobs/$LAST_TAG_JOB_ID/artifacts/raw/ligo"
     - SRI_LIGO_BINARY_HASH=$(nix --extra-experimental-features nix-command hash to-sri --type sha256 $(nix-prefetch-url --type sha256 --quiet $BINARY_GITLAB_ARTIFACT_URL))
     - echo "SRI_LIGO_BINARY_HASH=${SRI_LIGO_BINARY_HASH}" >> nixSriLigoBinary.env
   artifacts:
@@ -446,7 +446,7 @@ update-repository-status:
   script:
     - git submodule sync --recursive                       
     - git submodule update --init --recursive --remote --force
-    - git remote rm origin && git remote add origin "git@gitlab.com:ligolang/ligo.git"
+    - git remote rm origin && git remote add origin "git@gitlab.com:mavryk-network/ligo.git"
     - node scripts/manpages/manpages.js ./ligo
     - ./.ci/scripts/build_website_references_from_stdlib/main.sh ligo
     - ./.ci/scripts/versioning_website.sh $RELEASE_VERSION
diff --git a/.ci/scripts/AUR/template/template.PKGBUILD b/.ci/scripts/AUR/template/template.PKGBUILD
index a7972ee052..8de2a66cad 100644
--- a/.ci/scripts/AUR/template/template.PKGBUILD
+++ b/.ci/scripts/AUR/template/template.PKGBUILD
@@ -3,7 +3,7 @@ pkgname=ligo-bin
 pkgver=LIGO_VERSION_PLACEHOLDER
 pkgrel=1
 pkgdesc="High Level Smart Contract Language for Tezos (binary)"
-url="https://gitlab.com/ligolang/ligo"
+url="https://gitlab.com/mavryk-network/ligo"
 
 arch=('x86_64')
 license=('MIT')
diff --git a/.ci/scripts/homebrew/template/homebrew-template.rb b/.ci/scripts/homebrew/template/homebrew-template.rb
index 6cf1e21bd1..f267120e6b 100644
--- a/.ci/scripts/homebrew/template/homebrew-template.rb
+++ b/.ci/scripts/homebrew/template/homebrew-template.rb
@@ -4,9 +4,9 @@ class LIGO_CLASS_PLACEHOLDER < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "LIGO_VERSION_PLACEHOLDER", revision: "LIGO_HEAD_REF_HASH_PLACEHOLDER"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "LIGO_VERSION_PLACEHOLDER", revision: "LIGO_HEAD_REF_HASH_PLACEHOLDER"
   version "LIGO_VERSION_PLACEHOLDER"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/.ci/scripts/nix/update_ligo_default_nix_file.sh b/.ci/scripts/nix/update_ligo_default_nix_file.sh
index fee8629c22..e77a32a422 100755
--- a/.ci/scripts/nix/update_ligo_default_nix_file.sh
+++ b/.ci/scripts/nix/update_ligo_default_nix_file.sh
@@ -13,7 +13,7 @@ if [ "$(uname)" == "Darwin" ]; then
 fi
 
 # Replace SRI for nix
-SRI_LIGO_BINARY_HASH=$(nix --extra-experimental-features nix-command hash to-sri --type sha256 $(jq -r .sha256 <<< $(nix run nixpkgs#nix-prefetch-git -- --rev $VERSION --url https://gitlab.com/ligolang/ligo.git --fetch-submodules --quiet --no-deepClone)))
+SRI_LIGO_BINARY_HASH=$(nix --extra-experimental-features nix-command hash to-sri --type sha256 $(jq -r .sha256 <<< $(nix run nixpkgs#nix-prefetch-git -- --rev $VERSION --url https://gitlab.com/mavryk-network/ligo.git --fetch-submodules --quiet --no-deepClone)))
 echo "update distribution reference SRI_LIGO_BINARY_HASH = $SRI_LIGO_BINARY_HASH"
 
 # Idk why, all nixPkgs files are 644, so I change it temporarly to be able to edit it
diff --git a/.ci/scripts/update_distribution_references_with_release.sh b/.ci/scripts/update_distribution_references_with_release.sh
index 9f76b710d1..3cd61a5cfa 100755
--- a/.ci/scripts/update_distribution_references_with_release.sh
+++ b/.ci/scripts/update_distribution_references_with_release.sh
@@ -10,12 +10,12 @@ ROOT_FOLDER="../.."
 DISTRIBUTION_URL_PATTERN_DEB_NEXT="https://ligolang.org/deb/ligo.deb"
 DISTRIBUTION_URL_PATTERN_BINARY_NEXT="https://ligolang.org/bin/linux/ligo"
 
-DISTRIBUTION_URL_GITLAB_ARTIFACT_REGEX_PATTERN_RELEASE="(.*https://gitlab\.com/ligolang/ligo/-/jobs/)[0-9]{10}(/artifacts/raw\/(ligo\.deb|ligo))"
+DISTRIBUTION_URL_GITLAB_ARTIFACT_REGEX_PATTERN_RELEASE="(.*https://gitlab\.com/mavryk-network/ligo/-/jobs/)[0-9]{10}(/artifacts/raw\/(ligo\.deb|ligo))"
 
 VERSION_REGEX_PATTERN="ligo:[0-9]+\.[0-9]+\.[0-9]+"
 
-DEB_GITLAB_ARTIFACT_URL="https://gitlab.com/ligolang/ligo/-/jobs/$1/artifacts/raw/ligo.deb"
-BINARY_GITLAB_ARTIFACT_URL="https://gitlab.com/ligolang/ligo/-/jobs/$1/artifacts/raw/ligo"
+DEB_GITLAB_ARTIFACT_URL="https://gitlab.com/mavryk-network/ligo/-/jobs/$1/artifacts/raw/ligo.deb"
+BINARY_GITLAB_ARTIFACT_URL="https://gitlab.com/mavryk-network/ligo/-/jobs/$1/artifacts/raw/ligo"
 
 FILES_PATH_TO_EDIT=(
     "$ROOT_FOLDER/tools/webide-new/ligo-webide-backend/Dockerfile"
diff --git a/HomebrewFormula/ligo.rb b/HomebrewFormula/ligo.rb
index cbad860bc5..dd252fe70b 100644
--- a/HomebrewFormula/ligo.rb
+++ b/HomebrewFormula/ligo.rb
@@ -4,9 +4,9 @@ class Ligo < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.4.0", revision: "86548dbd16776c30fd47e5fdf48631cfffecaea3"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.4.0", revision: "86548dbd16776c30fd47e5fdf48631cfffecaea3"
   version "1.4.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.63.2.rb b/HomebrewFormula/ligo@0.63.2.rb
index 230a1a9db6..72f8c8a472 100644
--- a/HomebrewFormula/ligo@0.63.2.rb
+++ b/HomebrewFormula/ligo@0.63.2.rb
@@ -4,9 +4,9 @@ class LigoAT0632 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.63.2", revision: "edaeecfc20ccb598a2cf97348df847762d36cac8"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.63.2", revision: "edaeecfc20ccb598a2cf97348df847762d36cac8"
   version "0.63.2"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.66.0.rb b/HomebrewFormula/ligo@0.66.0.rb
index b898962f6b..d5c8ba34f1 100644
--- a/HomebrewFormula/ligo@0.66.0.rb
+++ b/HomebrewFormula/ligo@0.66.0.rb
@@ -4,9 +4,9 @@ class LigoAT0660 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.66.0", revision: "e003f647fd090a18de2086e2e2b8821981a6a33b"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.66.0", revision: "e003f647fd090a18de2086e2e2b8821981a6a33b"
   version "0.66.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.67.1.rb b/HomebrewFormula/ligo@0.67.1.rb
index 2823b7e011..8670e54d90 100644
--- a/HomebrewFormula/ligo@0.67.1.rb
+++ b/HomebrewFormula/ligo@0.67.1.rb
@@ -4,9 +4,9 @@ class LigoAT0671 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.67.1", revision: "48e82e0f27e5c5ac6a360b2973a8df2f8420caf7"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.67.1", revision: "48e82e0f27e5c5ac6a360b2973a8df2f8420caf7"
   version "0.67.1"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.68.0.rb b/HomebrewFormula/ligo@0.68.0.rb
index 405965803c..01e714d943 100644
--- a/HomebrewFormula/ligo@0.68.0.rb
+++ b/HomebrewFormula/ligo@0.68.0.rb
@@ -4,9 +4,9 @@ class LigoAT0680 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.68.0", revision: "f23d9cf9807ca8ccab05c83d42a9df3066f695b3"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.68.0", revision: "f23d9cf9807ca8ccab05c83d42a9df3066f695b3"
   version "0.68.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.69.0.rb b/HomebrewFormula/ligo@0.69.0.rb
index e4259988bd..cc6338fab0 100644
--- a/HomebrewFormula/ligo@0.69.0.rb
+++ b/HomebrewFormula/ligo@0.69.0.rb
@@ -4,9 +4,9 @@ class LigoAT0690 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.69.0", revision: "d63c34412535fadfd98859dd8dad630fe08e90c2"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.69.0", revision: "d63c34412535fadfd98859dd8dad630fe08e90c2"
   version "0.69.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.70.0.rb b/HomebrewFormula/ligo@0.70.0.rb
index b68898a778..c68584874f 100644
--- a/HomebrewFormula/ligo@0.70.0.rb
+++ b/HomebrewFormula/ligo@0.70.0.rb
@@ -4,9 +4,9 @@ class LigoAT0700 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.70.0", revision: "709efd88f1ddcdf44a2e91400ad912b2f0b14e0e"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.70.0", revision: "709efd88f1ddcdf44a2e91400ad912b2f0b14e0e"
   version "0.70.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.70.1.rb b/HomebrewFormula/ligo@0.70.1.rb
index fb3f71afb2..3532106413 100644
--- a/HomebrewFormula/ligo@0.70.1.rb
+++ b/HomebrewFormula/ligo@0.70.1.rb
@@ -4,9 +4,9 @@ class LigoAT0701 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.70.1", revision: "06791c7c53c9ab0a519af7472c699372377def11"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.70.1", revision: "06791c7c53c9ab0a519af7472c699372377def11"
   version "0.70.1"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.71.0.rb b/HomebrewFormula/ligo@0.71.0.rb
index 24a97439a2..f0350cc906 100644
--- a/HomebrewFormula/ligo@0.71.0.rb
+++ b/HomebrewFormula/ligo@0.71.0.rb
@@ -4,9 +4,9 @@ class LigoAT0710 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.71.0", revision: "bdd69fa7cd9adc8756ca9e688ede0335672e29cf"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.71.0", revision: "bdd69fa7cd9adc8756ca9e688ede0335672e29cf"
   version "0.71.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.71.1.rb b/HomebrewFormula/ligo@0.71.1.rb
index 3e96f4c3c3..2aa266ba41 100644
--- a/HomebrewFormula/ligo@0.71.1.rb
+++ b/HomebrewFormula/ligo@0.71.1.rb
@@ -4,9 +4,9 @@ class LigoAT0711 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.71.1", revision: "2d557873ccd14e03e3ad42ed46a88571f4eeafab"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.71.1", revision: "2d557873ccd14e03e3ad42ed46a88571f4eeafab"
   version "0.71.1"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.72.0.rb b/HomebrewFormula/ligo@0.72.0.rb
index 86ba5a2079..0d285898ac 100644
--- a/HomebrewFormula/ligo@0.72.0.rb
+++ b/HomebrewFormula/ligo@0.72.0.rb
@@ -4,9 +4,9 @@ class LigoAT0720 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.72.0", revision: "d59593717f7600faba4d20d4a2a2fe851df96317"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.72.0", revision: "d59593717f7600faba4d20d4a2a2fe851df96317"
   version "0.72.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@0.73.0.rb b/HomebrewFormula/ligo@0.73.0.rb
index 3ad4b26213..a1bda60f1c 100644
--- a/HomebrewFormula/ligo@0.73.0.rb
+++ b/HomebrewFormula/ligo@0.73.0.rb
@@ -4,9 +4,9 @@ class LigoAT0730 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "0.73.0", revision: "48b0382cbd8be4c0be5140b952be780313861593"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "0.73.0", revision: "48b0382cbd8be4c0be5140b952be780313861593"
   version "0.73.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@1.0.0.rb b/HomebrewFormula/ligo@1.0.0.rb
index a0e94120df..331ea0b1df 100644
--- a/HomebrewFormula/ligo@1.0.0.rb
+++ b/HomebrewFormula/ligo@1.0.0.rb
@@ -4,9 +4,9 @@ class LigoAT100 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.0.0", revision: "a392154388b1abe974f424b71a66d618010f9e95"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.0.0", revision: "a392154388b1abe974f424b71a66d618010f9e95"
   version "1.0.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@1.1.0.rb b/HomebrewFormula/ligo@1.1.0.rb
index e9f175632d..12c85f1023 100644
--- a/HomebrewFormula/ligo@1.1.0.rb
+++ b/HomebrewFormula/ligo@1.1.0.rb
@@ -4,9 +4,9 @@ class LigoAT110 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.1.0", revision: "edcf7f67c70016705068934d29dfcd531f6908f0"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.1.0", revision: "edcf7f67c70016705068934d29dfcd531f6908f0"
   version "1.1.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@1.2.0.rb b/HomebrewFormula/ligo@1.2.0.rb
index 210e18a380..d39a5d9dff 100644
--- a/HomebrewFormula/ligo@1.2.0.rb
+++ b/HomebrewFormula/ligo@1.2.0.rb
@@ -4,9 +4,9 @@ class LigoAT120 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.2.0", revision: "2c62623f2593fff02ac27154ceaa5e6e3bbb8d5c"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.2.0", revision: "2c62623f2593fff02ac27154ceaa5e6e3bbb8d5c"
   version "1.2.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@1.3.0.rb b/HomebrewFormula/ligo@1.3.0.rb
index cbf0ed7afe..93c68bea66 100644
--- a/HomebrewFormula/ligo@1.3.0.rb
+++ b/HomebrewFormula/ligo@1.3.0.rb
@@ -4,9 +4,9 @@ class LigoAT130 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.3.0", revision: ""
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.3.0", revision: ""
   version "1.3.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/HomebrewFormula/ligo@1.4.0.rb b/HomebrewFormula/ligo@1.4.0.rb
index 7a7756ba23..7e5f3710ad 100644
--- a/HomebrewFormula/ligo@1.4.0.rb
+++ b/HomebrewFormula/ligo@1.4.0.rb
@@ -4,9 +4,9 @@ class LigoAT140 < Formula
   license "MIT"
 
   # We clone repo explicitely to preserve the information about git submodules
-  url "https://gitlab.com/ligolang/ligo.git", tag: "1.4.0", revision: "86548dbd16776c30fd47e5fdf48631cfffecaea3"
+  url "https://gitlab.com/mavryk-network/ligo.git", tag: "1.4.0", revision: "86548dbd16776c30fd47e5fdf48631cfffecaea3"
   version "1.4.0"
-  head "https://gitlab.com/ligolang/ligo.git", branch: "dev"
+  head "https://gitlab.com/mavryk-network/ligo.git", branch: "dev"
 
 
   bottle do
diff --git a/changelog/1722 b/changelog/1722
index 3a603fcf76..0746dac675 100644
--- a/changelog/1722
+++ b/changelog/1722
@@ -1,5 +1,5 @@
 author: nicolas.van.phan
-description: Closes(https://gitlab.com/ligolang/ligo/-/issues/1390)
+description: Closes(https://gitlab.com/mavryk-network/ligo/-/issues/1390)
 merge_request: '1722'
 title: Typer context - Replace lists by maps
 type: fixed
diff --git a/changelog/1937 b/changelog/1937
index e9faa4bcc5..b07b0b64c0 100644
--- a/changelog/1937
+++ b/changelog/1937
@@ -1,5 +1,5 @@
 author: Laucans
-description: \nRun `nix run gitlab:ligolang/ligo` to execute the last release of ligo
+description: \nRun `nix run gitlab:mavryk-network/ligo` to execute the last release of ligo
   binary through [nix](https://nixos.org) (arch x86_64-linux)
 merge_request: '1937'
 title: Execute ligo through NIX
diff --git a/changelog/1950 b/changelog/1950
index da978a581c..6625859005 100644
--- a/changelog/1950
+++ b/changelog/1950
@@ -1,8 +1,8 @@
 author: Laucans
 description: '\nAdd ligo installation through brew package manager. \nBy using \n\n```\nbrew
-  tap ligolang/ligo https://gitlab.com/ligolang/ligo.git\nbrew install ligolang/ligo/ligo\n\n```\nYou
+  tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git\nbrew install mavryk-network/ligo/ligo\n\n```\nYou
   can also install one of the three last version by targeting the version after \"@\"
-  : \n\n```\nbrew install ligolang/ligo/ligo@0.49.0\n\n```'
+  : \n\n```\nbrew install mavryk-network/ligo/ligo@0.49.0\n\n```'
 merge_request: '1950'
 title: add brew formula into ligo monorepo
 type: added
diff --git a/changelog/1974 b/changelog/1974
index 390185b802..3f501c1f78 100644
--- a/changelog/1974
+++ b/changelog/1974
@@ -1,6 +1,6 @@
 author: ulrikstrid
 description: '#### nix improvements\n\nAdd package that provides `ligo` with with `esy`.\nUsage:
-  `nix run gitlab:ligolang/ligo#withEsy -- install`'
+  `nix run gitlab:mavryk-network/ligo#withEsy -- install`'
 merge_request: '1974'
 title: Adds a package wrapped in esy
 type: added
diff --git a/changelog/2038 b/changelog/2038
index 801c8e7f68..f125e8668f 100644
--- a/changelog/2038
+++ b/changelog/2038
@@ -1,6 +1,6 @@
 
 author: lesenechal.remi & melwyn95
-description: '\n \n\n\nFix a bug where top-level let destructuring were causing code to be executed multiple time, as in:\n```\nlet (a,a) =\n  let () = Test.log "hello" in\n  (1,2)\n\n```\nFix a bug where type parameters were not found ([https://gitlab.com/ligolang/ligo/-/issues/1482](https://gitlab.com/ligolang/ligo/-/issues/1482))`proxy_tickets` code has been changed (see [https://ligolang.org/docs/advanced/testing/#transfers-and-originations-with-tickets](https://ligolang.org/docs/advanced/testing/#transfers-and-originations-with-tickets))\n'
+description: '\n \n\n\nFix a bug where top-level let destructuring were causing code to be executed multiple time, as in:\n```\nlet (a,a) =\n  let () = Test.log "hello" in\n  (1,2)\n\n```\nFix a bug where type parameters were not found ([https://gitlab.com/mavryk-network/ligo/-/issues/1482](https://gitlab.com/mavryk-network/ligo/-/issues/1482))`proxy_tickets` code has been changed (see [https://ligolang.org/docs/advanced/testing/#transfers-and-originations-with-tickets](https://ligolang.org/docs/advanced/testing/#transfers-and-originations-with-tickets))\n'
 merge_request: '2038'
 title: Add support for patterns in top-level declarations
 type: fixed
diff --git a/changelog/2223 b/changelog/2223
index c9adab6396..d645dd654f 100644
--- a/changelog/2223
+++ b/changelog/2223
@@ -1,6 +1,6 @@
 
 author: er433
-description: "\\nBy default, Lima protocol is used as current. This affects compilation of certain primitives (such as `Tezos.create_ticket` and contracts using `chest`, [see changelog for Lima protocol introduction for more information](https://gitlab.com/ligolang/ligo/-/merge_requests/2094#changelog)).\\n\\nKathmandu can still be used passing the flag `--protocol kathmandu`.\\n\\n"
+description: "\\nBy default, Lima protocol is used as current. This affects compilation of certain primitives (such as `Tezos.create_ticket` and contracts using `chest`, [see changelog for Lima protocol introduction for more information](https://gitlab.com/mavryk-network/ligo/-/merge_requests/2094#changelog)).\\n\\nKathmandu can still be used passing the flag `--protocol kathmandu`.\\n\\n"
 merge_request: '2223'
 title: "Set `current` protocol to Lima"
 type: breaking
diff --git a/changelog/2393 b/changelog/2393
index d63cc9ecf5..27dbb1668b 100644
--- a/changelog/2393
+++ b/changelog/2393
@@ -1,6 +1,6 @@
 
 author: heitor.toledo
-description: "\\n\\nAdd a new subcommand (`ligo lsp`) whose purpose is to allow LSP clients (Visual Studio Code, Emacs, Vim, etc) to communicate with the new LIGO Language Server, which is being rewritten in OCaml. This command is not meant to be launched manually by users, but rather by editors. The rewrite was officially made in [!2303](https://gitlab.com/ligolang/ligo/-/merge_requests/2303).\\n\\nThe initial release supports diagnostics (errors only), go to definition, hover, rename (only in open files), references (only in open files), and type definition.\\n\\nAs the rewrite is new, it does not yet support feature parity with the old language server, and bugs are to be expected.\\n\\nOther LSP features (hover, folding range, document link, warnings for diagnostics, prepare rename) have since been implemented in other merge requests.\\n\\nOfficial support for the Vim, Emacs, and Visual Studio Code plugins will come soon, as well as the VS Code plugin release on the Marketplace and OpenVSX.\\n\\n"
+description: "\\n\\nAdd a new subcommand (`ligo lsp`) whose purpose is to allow LSP clients (Visual Studio Code, Emacs, Vim, etc) to communicate with the new LIGO Language Server, which is being rewritten in OCaml. This command is not meant to be launched manually by users, but rather by editors. The rewrite was officially made in [!2303](https://gitlab.com/mavryk-network/ligo/-/merge_requests/2303).\\n\\nThe initial release supports diagnostics (errors only), go to definition, hover, rename (only in open files), references (only in open files), and type definition.\\n\\nAs the rewrite is new, it does not yet support feature parity with the old language server, and bugs are to be expected.\\n\\nOther LSP features (hover, folding range, document link, warnings for diagnostics, prepare rename) have since been implemented in other merge requests.\\n\\nOfficial support for the Vim, Emacs, and Visual Studio Code plugins will come soon, as well as the VS Code plugin release on the Marketplace and OpenVSX.\\n\\n"
 merge_request: '2393'
 title: "[Chore] Add a changelog documenting the initial write of the LSP"
 type: added
diff --git a/changelog/2503 b/changelog/2503
index 3cb159226b..fb732e8792 100644
--- a/changelog/2503
+++ b/changelog/2503
@@ -1,6 +1,6 @@
 
 author: heitor.toledo
-description: "\\n\\nThe LIGO Language Server now supports a few new changes and fixes related to configuration, notably:\\n\\nIt's now possible to disable specific features from the Visual Studio Code extension. Check the [README](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vscode/README.md) for more details.Fixed an exception that would be thrown when using the language server with Emacs related to decoding `null` from the configuration.The language server now respects `Deprecated` from the Visual Studio Code configuration and emits a warning when opening a PascaLIGO file if that is not set.Configuration changes may now be done dynamically. Previously, a language server restart would be required for changes to take effect.\\n"
+description: "\\n\\nThe LIGO Language Server now supports a few new changes and fixes related to configuration, notably:\\n\\nIt's now possible to disable specific features from the Visual Studio Code extension. Check the [README](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vscode/README.md) for more details.Fixed an exception that would be thrown when using the language server with Emacs related to decoding `null` from the configuration.The language server now respects `Deprecated` from the Visual Studio Code configuration and emits a warning when opening a PascaLIGO file if that is not set.Configuration changes may now be done dynamically. Previously, a language server restart would be required for changes to take effect.\\n"
 merge_request: '2503'
 title: "[#1658] Support configuration: part 2"
 type: added
diff --git a/changelog/2993 b/changelog/2993
index 10b3dd51b1..4d93459fc2 100644
--- a/changelog/2993
+++ b/changelog/2993
@@ -1,6 +1,6 @@
 
 author: DK318
-description: "Added a `ligo doc` command which will generate documentation for your project. At this moment only JsLIGO is supported and it requires `typedoc` to be installed.\\n\\nRelated [MR](https://gitlab.com/ligolang/ligo/-/merge_requests/2993)\\n\\n\\n"
+description: "Added a `ligo doc` command which will generate documentation for your project. At this moment only JsLIGO is supported and it requires `typedoc` to be installed.\\n\\nRelated [MR](https://gitlab.com/mavryk-network/ligo/-/merge_requests/2993)\\n\\n\\n"
 merge_request: '2993'
 title: "Draft: [#2094] Translate `Ast_typed` into TypeScript for docs generation"
 type: added
diff --git a/changelog/3031 b/changelog/3031
index a13f95613d..ee06908ed6 100644
--- a/changelog/3031
+++ b/changelog/3031
@@ -1,6 +1,6 @@
 
 author: DK318
-description: "Added CLI autocompletion script. All the instructions are available in [README.md](https://gitlab.com/ligolang/ligo/-/blob/dk318/%232120-implement-cli-autocompletions/tools/autocompletion/README.md)\\n\\n\\n"
+description: "Added CLI autocompletion script. All the instructions are available in [README.md](https://gitlab.com/mavryk-network/ligo/-/blob/dk318/%232120-implement-cli-autocompletions/tools/autocompletion/README.md)\\n\\n\\n"
 merge_request: '3031'
 title: "[#2120] Implement autocompletion for CLI"
 type: added
diff --git a/gitlab-pages/docs/contributors/documentation-and-releases.md b/gitlab-pages/docs/contributors/documentation-and-releases.md
index 2c3199a15d..1a5cb8f357 100644
--- a/gitlab-pages/docs/contributors/documentation-and-releases.md
+++ b/gitlab-pages/docs/contributors/documentation-and-releases.md
@@ -46,4 +46,4 @@ Development releases of LIGO are tagged `next` and are built with each commit to
 
 ### Stable releases
 
-Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/ligolang/ligo/-/releases and pushing images to docker.
+Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/mavryk-network/ligo/-/releases and pushing images to docker.
diff --git a/gitlab-pages/docs/contributors/ligo_test_guide.md b/gitlab-pages/docs/contributors/ligo_test_guide.md
index f5b3b0942d..0fee487366 100644
--- a/gitlab-pages/docs/contributors/ligo_test_guide.md
+++ b/gitlab-pages/docs/contributors/ligo_test_guide.md
@@ -7,9 +7,9 @@ Bonus: you will become more familiar with LIGO in the process!
 Tests are written in OCaml, as LIGO doesn't (yet) have a good way to do automated testing. Thankfully the test code is typically less demanding than the features being tested.
 
 Tests are currently contained in
-[src/test](https://gitlab.com/ligolang/ligo/tree/dev/src/test), but
+[src/test](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test), but
 most are integration tests which rely on test contracts kept in
-[src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts). If
+[src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts). If
 you are new to LIGO, reading these contracts can be a useful
 introduction to a particular LIGO syntax.
 
@@ -34,7 +34,7 @@ LIGO is divided into two parts
 - the **front end** handles syntax
 - the **backend** optimises and compiles a core language shared between syntaxes
 
-You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/ligolang/ligo/tree/dev/src/passes/01-parsing).
+You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/mavryk-network/ligo/tree/dev/src/passes/01-parsing).
 
 ### Two Useful Test Cases Using LIGO
 
@@ -65,9 +65,9 @@ a useful supplement to human testing.
 LIGO's OCaml-based tests are written in
 [alcotest](https://github.com/mirage/alcotest/). However, the tests
 you encounter in
-[src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml)
+[src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml)
 are built on top of some abstractions, currently defined in
-[src/test/test_helpers.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/test_helpers.ml). The
+[src/test/test_helpers.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/test_helpers.ml). The
 use of these can be inferred fairly well from looking at existing
 tests, but let us break a few of them down for analysis.
 
@@ -136,7 +136,7 @@ convert our expected test values into LIGO expressions and
 data. Constructors such as `e_list` and `e_address` provide a bridge
 between LIGO and OCaml. Their definitions can be found in files such
 as
-[src/stages/ast_core/combinators.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/stages/ast_core/combinators.ml),
+[src/stages/ast_core/combinators.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/stages/ast_core/combinators.ml),
 or using
 [Merlin's definition point finder](https://github.com/ocaml/merlin/wiki). These
 same functions are used during the simplification stage of LIGO
@@ -149,8 +149,8 @@ What if we want to write a test of our own? If the test is in the
 integration test vein (which it probably is if you are testing new
 syntax or features), then the process looks something like:
 
-1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts).
-2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
+1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts).
+2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
 3. Write the feature, assuming it does not already exist. Build the
    resulting version of LIGO without errors.
 4. Run the test suite, see if your test(s) pass. If they do, you are
diff --git a/gitlab-pages/docs/demo/ligo-snippet.md b/gitlab-pages/docs/demo/ligo-snippet.md
index fd924cfeb7..8c57550b72 100644
--- a/gitlab-pages/docs/demo/ligo-snippet.md
+++ b/gitlab-pages/docs/demo/ligo-snippet.md
@@ -6,7 +6,7 @@ title: LIGO snippets Demo
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-“ligo-snippets” (https://www.npmjs.com/package/@ligolang/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
+“ligo-snippets” (https://www.npmjs.com/package/@mavryk-network/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
 
 The user will see LIGO code with syntax highlighting, and an action button allowing the user to open the source code in the LIGO Web IDE (https://ide.ligolang.org).
 
diff --git a/gitlab-pages/docs/faq/v1-migration-guide.md b/gitlab-pages/docs/faq/v1-migration-guide.md
index 01c343ff0a..48abc29470 100644
--- a/gitlab-pages/docs/faq/v1-migration-guide.md
+++ b/gitlab-pages/docs/faq/v1-migration-guide.md
@@ -26,12 +26,12 @@ Another consequence of this change is that, when originating a contract for test
 We are also rolling out a new feature allowing the addition, removal and update of dynamic entry points for a contract after deployment. This could be a useful feature for example when building a DAO which allows on-chain vote to upgrade its code (or a DAO which controls the code of another separate contract). For more information, see [the documentation](../advanced/dynamic-entrypoints.md) and [the reference](../reference/Dynamic_entrypoints.md) for this feature.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2818
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2814
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2810
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2805
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2831
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2885
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2818
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2814
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2810
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2805
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2831
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2885
 
 #### Uniform calling convention for views and entry points.
 
@@ -84,11 +84,11 @@ const get_storage = (_: unit, storage: int): int => storage
 
 #### `contract_of` and `parameter_of`
 
-The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
+The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2685
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2685
 
 ### `export` and `@private` now have the expected effect
 
@@ -109,8 +109,8 @@ const y = Foo.Bar.x
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2796
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2796
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
 
 ### The comb layout is now used by default
 
@@ -125,7 +125,7 @@ If your project has a stable ABI that other tools rely on, you might need to man
 Once reaching the optimization phase of your development process, youu may wish to try annotating large variants (which contain many cases) with `@layout("tree")` / `[@layout tree]` and comparing the size and gas consumption of the compiled contracts.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/1816.
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/1816.
 
 ### A small set of annotations / decorators are now supported
 
@@ -159,11 +159,11 @@ There are also two internal annotations / decorators, which should not appear in
 * `@hidden`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/ligolang/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
 
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
 
 ### Field and tuple component access
 
@@ -178,14 +178,14 @@ const stuff = {
 const part : bool = stuff.y["universe"][2];
 ```
 
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Miscellaneous
 
-* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2690.
-* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/ligolang/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/ligolang/ligo/-/merge_requests/2455 and https://gitlab.com/ligolang/ligo/-/merge_requests/2607.
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2501
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2500
+* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2690.
+* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2455 and https://gitlab.com/mavryk-network/ligo/-/merge_requests/2607.
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2501
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2500
 
 ## JsLIGO
 
@@ -194,8 +194,8 @@ const part : bool = stuff.y["universe"][2];
 You can now write `3mav` or `3mumav` instead of `3 as mav` or `3 as mumav`. This convenient feature was already present in CameLIGO and is now available in JsLIGO too!
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2853
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2853
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### New bitwise operators
 
@@ -227,7 +227,7 @@ const zero_bytes : bytes = 0x01 >> 1n
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Changes to pattern matching
 
@@ -296,7 +296,7 @@ Furthermore, there are a few changes to how patterns are written:
 * Patterns with one variable per parameter are written as expected: `Foo: (a, b) => a + b` becomes `when(Foo(a, b)): a + b`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 
 ### `_` is now a valid variable name and can't be used for its former throw-away semantics
@@ -331,7 +331,7 @@ const f = () => {
 If multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript. However, it is still possible to shadow a `_` within a smaller scope, e.g. if `_` is globally defined as an alias for another module, a function can still specify `_` as an argument name and shadow the global definition, which could cause issues. It is wise to skim over existing code for such cases.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2674
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2674
 
 ### Imports are now automatically re-exported
 
@@ -340,11 +340,11 @@ When a module is imported e.g. with `#import "foo.jsligo" "Foo"` inside the file
 For example, a third file importing `bar.jsligo` as `Bar` can write `Bar.Foo.x` to access the `x` defined in `foo.jsligo`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2815
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2815
 
 ### Miscellaneous
 
-* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ## CameLIGO
 
@@ -362,7 +362,7 @@ let part : bool = stuff.y.2.universe
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Package management: use ligo.json instead of package.json or esy.json
 
@@ -371,8 +371,8 @@ Users often work with JaveScript toolchain alongside ours. Using package.json to
 As part of this change, we are no longer using the `esy` tool for package management, and the `installation.json` file, formerly located at `_esy/ligo/installation.json`, should now be moved to `_ligo/ligo/installation.json`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2817
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2785
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2883
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2817
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2785
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2883
 
 <!-- updated use of entry -->
diff --git a/gitlab-pages/docs/intro/editor-support.md b/gitlab-pages/docs/intro/editor-support.md
index 8b63670043..fd5caca6ff 100644
--- a/gitlab-pages/docs/intro/editor-support.md
+++ b/gitlab-pages/docs/intro/editor-support.md
@@ -7,8 +7,8 @@ Painters need a brush and a canvas. Developers need a good IDE experience. LIGO
 
 - **[Install the LIGO extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)**
 
-- **[Install the LIGO extension for VIM](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
+- **[Install the LIGO extension for VIM](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
 
-- **[Install the LIGO extension for Emacs](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/emacs/README.md)**
+- **[Install the LIGO extension for Emacs](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/emacs/README.md)**
 
 <!-- updated use of entry -->
\ No newline at end of file
diff --git a/gitlab-pages/docs/intro/installation.md b/gitlab-pages/docs/intro/installation.md
index 2355af16e9..8d298214e7 100644
--- a/gitlab-pages/docs/intro/installation.md
+++ b/gitlab-pages/docs/intro/installation.md
@@ -14,7 +14,7 @@ You can also try LIGO in a Gitpod environment
 
 ## Releases
 
-Releases are available at the [releases page of GitLab project](https://gitlab.com/ligolang/ligo/-/releases). All the artifacts are attached there.
+Releases are available at the [releases page of GitLab project](https://gitlab.com/mavryk-network/ligo/-/releases). All the artifacts are attached there.
 
 If you wish to see the changelog, you can either run `ligo changelog` or go to [this page](https://ligolang.org/docs/next/intro/changelog). It contains links to corresponding releases, should you wish to download the artifacts.
 
@@ -33,14 +33,14 @@ If you wish to see the changelog, you can either run `ligo changelog` or go to [
 
 The `ligo` executable is statically linked. It should run on most modern Linux distributions.
 
-You can get the rolling release [here](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
+You can get the rolling release [here](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
 
 ```zsh
-wget https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo
+wget https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo
 chmod +x ./ligo
 ```
 
-For a specific version, you can visit our [release page](https://gitlab.com/ligolang/ligo/-/releases/).  
+For a specific version, you can visit our [release page](https://gitlab.com/mavryk-network/ligo/-/releases/).  
 Optionally, you can put it somewhere in your `PATH` for easy access:
 
 ```zsh
@@ -52,22 +52,22 @@ sudo cp ./ligo /usr/local/bin
 Try our tap :
 
 ```bash
-brew tap ligolang/ligo https://gitlab.com/ligolang/ligo.git
-brew install ligolang/ligo/ligo
+brew tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git
+brew install mavryk-network/ligo/ligo
 ```
 
 To upgrade ligo :
 
 ```bash
 brew update
-brew upgrade ligolang/ligo/ligo
+brew upgrade mavryk-network/ligo/ligo
 ```
 
 </TabItem>
 <TabItem value="deb">
 
 A `.deb` package containing the static `ligo` executable is also available.
-First, download [the package](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
+First, download [the package](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
 
 ```zsh
 sudo apt install ./ligo.deb
@@ -96,18 +96,18 @@ If you've [installed 🐳 Docker](https://docs.docker.com/install/), you can run
 
 Linux or OSX:
 > ```sh
-> docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0
+> docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0
 > ```
 > For convenience you can alias the above command
 > ```sh
-> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0'
+> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0'
 > ```
 > To make this `alias` persistent across terminal sessions you need to configure your shell.     
 > Here is a [good link](https://www.tecmint.com/create-alias-in-linux/) with the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 <TabItem value="windows">
@@ -115,18 +115,18 @@ Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/l
 It's possible to use ligo in [Docker](https://docs.docker.com/install/) through docker or [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install)
 
 > ```dos
-> docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0`
+> docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0`
 > ```
 > For convenience you can alias the above command
 > ```dos
-> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0 $*
+> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0 $*
 > ```
 > To make the alias persistent across terminal sessions you need to add the `doskey` to the Windows Registry.  
 > Follow [this stackoverflow answer](https://stackoverflow.com/a/21040825) for the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 </Tabs>
diff --git a/gitlab-pages/docs/intro/ligo-intro.md b/gitlab-pages/docs/intro/ligo-intro.md
index 251bc0b000..91da7a7075 100644
--- a/gitlab-pages/docs/intro/ligo-intro.md
+++ b/gitlab-pages/docs/intro/ligo-intro.md
@@ -84,7 +84,7 @@ For critical code, LIGO also keeps its compiled output unbloated making **possib
   [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Understand and troubleshoot your code with the debugger available in [vscode extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Integrate LIGO to your pipeline with [ligo github action](https://github.com/marigold-dev/ligo-action)
-- Test your documentation with [ligo-mdx](https://github.com/ligolang/ligo-mdx)
+- Test your documentation with [ligo-mdx](https://github.com/mavryk-network/ligo-mdx)
 
 ---
 
diff --git a/gitlab-pages/docs/language-basics/types.md b/gitlab-pages/docs/language-basics/types.md
index e6c1e5a2e2..ddcdc3044b 100644
--- a/gitlab-pages/docs/language-basics/types.md
+++ b/gitlab-pages/docs/language-basics/types.md
@@ -15,7 +15,7 @@ LIGO types are built on top of Michelson's type system.
 
 ## Built-in types
 
-For quick reference, you can find all the built-in types [here](https://gitlab.com/ligolang/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
+For quick reference, you can find all the built-in types [here](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
 
 ## Type aliases
 
diff --git a/gitlab-pages/docs/tutorials/inter-contract-calls/inter-contract-calls.md b/gitlab-pages/docs/tutorials/inter-contract-calls/inter-contract-calls.md
index c40660e7ad..3dddc537f9 100644
--- a/gitlab-pages/docs/tutorials/inter-contract-calls/inter-contract-calls.md
+++ b/gitlab-pages/docs/tutorials/inter-contract-calls/inter-contract-calls.md
@@ -278,7 +278,7 @@ let iswhitelisted (arg : address * (bool contract)) (s : storage) : operation li
 </Syntax>
 
 
-Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/ligolang/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
+Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/mavryk-network/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
 
 <Syntax syntax="cameligo">
 
diff --git a/gitlab-pages/website/docusaurus.config.js b/gitlab-pages/website/docusaurus.config.js
index febca51a3f..121bb0871b 100644
--- a/gitlab-pages/website/docusaurus.config.js
+++ b/gitlab-pages/website/docusaurus.config.js
@@ -160,12 +160,12 @@ const config = {
             items: [
               {
                 label: "Sources",
-                href: "https://gitlab.com/ligolang/ligo",
+                href: "https://gitlab.com/mavryk-network/ligo",
                 rel: "noopener noreferrer nofollow",
               },
               {
                 label: "Issues",
-                href: "https://gitlab.com/ligolang/ligo/-/issues",
+                href: "https://gitlab.com/mavryk-network/ligo/-/issues",
                 rel: "noopener noreferrer nofollow",
               },
               {
diff --git a/gitlab-pages/website/src/components/Community/index.tsx b/gitlab-pages/website/src/components/Community/index.tsx
index 840c63cdef..498edbcc7a 100644
--- a/gitlab-pages/website/src/components/Community/index.tsx
+++ b/gitlab-pages/website/src/components/Community/index.tsx
@@ -18,7 +18,7 @@ const Community = ({ discordMembers, contributors = 78, packages }: CommunityPro
         "Ligo is open-source and open for contributions. Join the Ligo team on GitLab and start contributing!",
       cta: {
         label: "contribute on gitlab",
-        href: "https://gitlab.com/ligolang/ligo",
+        href: "https://gitlab.com/mavryk-network/ligo",
         rel: "noopener noreferrer nofollow",
       },
     },
diff --git a/gitlab-pages/website/src/components/News/index.tsx b/gitlab-pages/website/src/components/News/index.tsx
index ff1236f36a..19d1d73a53 100644
--- a/gitlab-pages/website/src/components/News/index.tsx
+++ b/gitlab-pages/website/src/components/News/index.tsx
@@ -55,7 +55,7 @@ const News = () => {
       description:
         "Ligo sources are available on our GitLab. Feel free to open an issue or contribute.",
       size: "small",
-      href: "https://gitlab.com/ligolang/ligo",
+      href: "https://gitlab.com/mavryk-network/ligo",
 
       cta: "Contribute to Ligo",
     },
diff --git a/gitlab-pages/website/src/theme/Footer/Layout/index.js b/gitlab-pages/website/src/theme/Footer/Layout/index.js
index aae65a725a..dd627577dc 100644
--- a/gitlab-pages/website/src/theme/Footer/Layout/index.js
+++ b/gitlab-pages/website/src/theme/Footer/Layout/index.js
@@ -27,7 +27,7 @@ const COMMUNICATION_CHANNELS = [
     description: "See Ligo latest videos on YouTube",
   },
   {
-    link: "https://gitlab.com/ligolang/ligo/issues",
+    link: "https://gitlab.com/mavryk-network/ligo/issues",
     icon: {
       src: "img/communication_channels/gitlab.svg",
       width: "30",
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/documentation-and-releases.md b/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/documentation-and-releases.md
index 2c3199a15d..1a5cb8f357 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/documentation-and-releases.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/documentation-and-releases.md
@@ -46,4 +46,4 @@ Development releases of LIGO are tagged `next` and are built with each commit to
 
 ### Stable releases
 
-Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/ligolang/ligo/-/releases and pushing images to docker.
+Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/mavryk-network/ligo/-/releases and pushing images to docker.
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/ligo_test_guide.md b/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/ligo_test_guide.md
index f5b3b0942d..0fee487366 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/ligo_test_guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/contributors/ligo_test_guide.md
@@ -7,9 +7,9 @@ Bonus: you will become more familiar with LIGO in the process!
 Tests are written in OCaml, as LIGO doesn't (yet) have a good way to do automated testing. Thankfully the test code is typically less demanding than the features being tested.
 
 Tests are currently contained in
-[src/test](https://gitlab.com/ligolang/ligo/tree/dev/src/test), but
+[src/test](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test), but
 most are integration tests which rely on test contracts kept in
-[src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts). If
+[src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts). If
 you are new to LIGO, reading these contracts can be a useful
 introduction to a particular LIGO syntax.
 
@@ -34,7 +34,7 @@ LIGO is divided into two parts
 - the **front end** handles syntax
 - the **backend** optimises and compiles a core language shared between syntaxes
 
-You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/ligolang/ligo/tree/dev/src/passes/01-parsing).
+You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/mavryk-network/ligo/tree/dev/src/passes/01-parsing).
 
 ### Two Useful Test Cases Using LIGO
 
@@ -65,9 +65,9 @@ a useful supplement to human testing.
 LIGO's OCaml-based tests are written in
 [alcotest](https://github.com/mirage/alcotest/). However, the tests
 you encounter in
-[src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml)
+[src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml)
 are built on top of some abstractions, currently defined in
-[src/test/test_helpers.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/test_helpers.ml). The
+[src/test/test_helpers.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/test_helpers.ml). The
 use of these can be inferred fairly well from looking at existing
 tests, but let us break a few of them down for analysis.
 
@@ -136,7 +136,7 @@ convert our expected test values into LIGO expressions and
 data. Constructors such as `e_list` and `e_address` provide a bridge
 between LIGO and OCaml. Their definitions can be found in files such
 as
-[src/stages/ast_core/combinators.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/stages/ast_core/combinators.ml),
+[src/stages/ast_core/combinators.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/stages/ast_core/combinators.ml),
 or using
 [Merlin's definition point finder](https://github.com/ocaml/merlin/wiki). These
 same functions are used during the simplification stage of LIGO
@@ -149,8 +149,8 @@ What if we want to write a test of our own? If the test is in the
 integration test vein (which it probably is if you are testing new
 syntax or features), then the process looks something like:
 
-1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts).
-2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
+1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts).
+2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
 3. Write the feature, assuming it does not already exist. Build the
    resulting version of LIGO without errors.
 4. Run the test suite, see if your test(s) pass. If they do, you are
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/demo/ligo-snippet.md b/gitlab-pages/website/versioned_docs/version-1.2.0/demo/ligo-snippet.md
index def34f85a1..6b0da8b921 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/demo/ligo-snippet.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/demo/ligo-snippet.md
@@ -6,7 +6,7 @@ title: Ligo-Snippets Demo
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-“ligo-snippets” (https://www.npmjs.com/package/@ligolang/ligo-snippets) is a React component that can be included on any webpage to display Ligo source code to users.
+“ligo-snippets” (https://www.npmjs.com/package/@mavryk-network/ligo-snippets) is a React component that can be included on any webpage to display Ligo source code to users.
 
 The user will see Ligo code with syntax highlighting, and an action button allowing the user to open the source code in the Ligo Web IDE (https://ide.ligolang.org).
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/faq/v1-migration-guide.md b/gitlab-pages/website/versioned_docs/version-1.2.0/faq/v1-migration-guide.md
index 593e60720b..57f69d37f7 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/faq/v1-migration-guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/faq/v1-migration-guide.md
@@ -26,12 +26,12 @@ Another consequence of this change is that, when originating a contract for test
 We are also rolling out a new feature allowing the addition, removal and update of dynamic entry points for a contract after deployment. This could be a useful feature for example when building a DAO which allows on-chain vote to upgrade its code (or a DAO which controls the code of another separate contract). For more information, see [the documentation](../advanced/dynamic-entrypoints.md) and [the reference](../reference/dynamic_entrypoints.md) for this feature.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2818
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2814
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2810
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2805
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2831
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2885
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2818
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2814
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2810
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2805
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2831
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2885
 
 #### Uniform calling convention for views and entry points.
 
@@ -84,11 +84,11 @@ const get_storage = (_: unit, storage: int): int => storage
 
 #### `contract_of` and `parameter_of`
 
-The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
+The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2685
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2685
 
 ### `export` and `@private` now have the expected effect
 
@@ -109,8 +109,8 @@ const y = Foo.Bar.x
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2796
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2796
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
 
 ### The comb layout is now used by default
 
@@ -125,7 +125,7 @@ If your project has a stable ABI that other tools rely on, you might need to man
 Once reaching the optimization phase of your development process, youu may wish to try annotating large variants (which contain many cases) with `@layout("tree")` / `[@layout tree]` and comparing the size and gas consumption of the compiled contracts.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/1816.
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/1816.
 
 ### A small set of annotations / decorators are now supported
 
@@ -159,11 +159,11 @@ There are also two internal annotations / decorators, which should not appear in
 * `@hidden`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/ligolang/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
 
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
 
 ### Field and tuple component access
 
@@ -178,14 +178,14 @@ const stuff = {
 const part : bool = stuff.y["universe"][2];
 ```
 
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Miscellaneous
 
-* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2690.
-* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/ligolang/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/ligolang/ligo/-/merge_requests/2455 and https://gitlab.com/ligolang/ligo/-/merge_requests/2607.
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2501
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2500
+* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2690.
+* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2455 and https://gitlab.com/mavryk-network/ligo/-/merge_requests/2607.
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2501
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2500
 
 ## JsLIGO
 
@@ -194,8 +194,8 @@ const part : bool = stuff.y["universe"][2];
 You can now write `3mav` or `3mumav` instead of `3 as mav` or `3 as mumav`. This convenient feature was already present in CameLIGO and is now available in JsLIGO too!
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2853
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2853
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### New bitwise operators
 
@@ -227,7 +227,7 @@ const zero_bytes : bytes = 0x01 >> 1n
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Changes to pattern matching
 
@@ -296,7 +296,7 @@ Furthermore, there are a few changes to how patterns are written:
 * Patterns with one variable per parameter are written as expected: `Foo: (a, b) => a + b` becomes `when(Foo(a, b)): a + b`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 
 ### `_` is now a valid variable name and can't be used for its former throw-away semantics
@@ -331,7 +331,7 @@ const f = () => {
 If multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript. However, it is still possible to shadow a `_` within a smaller scope, e.g. if `_` is globally defined as an alias for another module, a function can still specify `_` as an argument name and shadow the global definition, which could cause issues. It is wise to skim over existing code for such cases.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2674
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2674
 
 ### Imports are now automatically re-exported
 
@@ -340,11 +340,11 @@ When a module is imported e.g. with `#import "foo.jsligo" "Foo"` inside the file
 For example, a third file importing `bar.jsligo` as `Bar` can write `Bar.Foo.x` to access the `x` defined in `foo.jsligo`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2815
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2815
 
 ### Miscellaneous
 
-* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ## CameLIGO
 
@@ -362,7 +362,7 @@ let part : bool = stuff.y.2.universe
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Package management: use ligo.json instead of package.json or esy.json
 
@@ -371,8 +371,8 @@ Users often work with JaveScript toolchain alongside ours. Using package.json to
 As part of this change, we are no longer using the `esy` tool for package management, and the `installation.json` file, formerly located at `_esy/ligo/installation.json`, should now be moved to `_ligo/ligo/installation.json`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2817
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2785
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2883
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2817
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2785
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2883
 
 <!-- updated use of entry -->
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/editor-support.md b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/editor-support.md
index 8b63670043..fd5caca6ff 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/editor-support.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/editor-support.md
@@ -7,8 +7,8 @@ Painters need a brush and a canvas. Developers need a good IDE experience. LIGO
 
 - **[Install the LIGO extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)**
 
-- **[Install the LIGO extension for VIM](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
+- **[Install the LIGO extension for VIM](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
 
-- **[Install the LIGO extension for Emacs](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/emacs/README.md)**
+- **[Install the LIGO extension for Emacs](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/emacs/README.md)**
 
 <!-- updated use of entry -->
\ No newline at end of file
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/installation.md b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/installation.md
index 2355af16e9..8d298214e7 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/installation.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/installation.md
@@ -14,7 +14,7 @@ You can also try LIGO in a Gitpod environment
 
 ## Releases
 
-Releases are available at the [releases page of GitLab project](https://gitlab.com/ligolang/ligo/-/releases). All the artifacts are attached there.
+Releases are available at the [releases page of GitLab project](https://gitlab.com/mavryk-network/ligo/-/releases). All the artifacts are attached there.
 
 If you wish to see the changelog, you can either run `ligo changelog` or go to [this page](https://ligolang.org/docs/next/intro/changelog). It contains links to corresponding releases, should you wish to download the artifacts.
 
@@ -33,14 +33,14 @@ If you wish to see the changelog, you can either run `ligo changelog` or go to [
 
 The `ligo` executable is statically linked. It should run on most modern Linux distributions.
 
-You can get the rolling release [here](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
+You can get the rolling release [here](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
 
 ```zsh
-wget https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo
+wget https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo
 chmod +x ./ligo
 ```
 
-For a specific version, you can visit our [release page](https://gitlab.com/ligolang/ligo/-/releases/).  
+For a specific version, you can visit our [release page](https://gitlab.com/mavryk-network/ligo/-/releases/).  
 Optionally, you can put it somewhere in your `PATH` for easy access:
 
 ```zsh
@@ -52,22 +52,22 @@ sudo cp ./ligo /usr/local/bin
 Try our tap :
 
 ```bash
-brew tap ligolang/ligo https://gitlab.com/ligolang/ligo.git
-brew install ligolang/ligo/ligo
+brew tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git
+brew install mavryk-network/ligo/ligo
 ```
 
 To upgrade ligo :
 
 ```bash
 brew update
-brew upgrade ligolang/ligo/ligo
+brew upgrade mavryk-network/ligo/ligo
 ```
 
 </TabItem>
 <TabItem value="deb">
 
 A `.deb` package containing the static `ligo` executable is also available.
-First, download [the package](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
+First, download [the package](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
 
 ```zsh
 sudo apt install ./ligo.deb
@@ -96,18 +96,18 @@ If you've [installed 🐳 Docker](https://docs.docker.com/install/), you can run
 
 Linux or OSX:
 > ```sh
-> docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0
+> docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0
 > ```
 > For convenience you can alias the above command
 > ```sh
-> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0'
+> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0'
 > ```
 > To make this `alias` persistent across terminal sessions you need to configure your shell.     
 > Here is a [good link](https://www.tecmint.com/create-alias-in-linux/) with the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 <TabItem value="windows">
@@ -115,18 +115,18 @@ Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/l
 It's possible to use ligo in [Docker](https://docs.docker.com/install/) through docker or [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install)
 
 > ```dos
-> docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0`
+> docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0`
 > ```
 > For convenience you can alias the above command
 > ```dos
-> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0 $*
+> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0 $*
 > ```
 > To make the alias persistent across terminal sessions you need to add the `doskey` to the Windows Registry.  
 > Follow [this stackoverflow answer](https://stackoverflow.com/a/21040825) for the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 </Tabs>
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/ligo-intro.md b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/ligo-intro.md
index ec2c1b240a..07a6221561 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/intro/ligo-intro.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/intro/ligo-intro.md
@@ -69,7 +69,7 @@ For critical code, LIGO also keeps its compiled output unbloated making **possib
 - Improve development experience with our lsp server available in [vscode extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Understand and troubleshoot your code with the debugger available in [vscode extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Integrate Ligo to your pipeline with [ligo github action](https://github.com/marigold-dev/ligo-action)
-- Test your documentation with [ligo-mdx](https://github.com/ligolang/ligo-mdx)
+- Test your documentation with [ligo-mdx](https://github.com/mavryk-network/ligo-mdx)
 
 ---
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/language-basics/types.md b/gitlab-pages/website/versioned_docs/version-1.2.0/language-basics/types.md
index e6c1e5a2e2..ddcdc3044b 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/language-basics/types.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/language-basics/types.md
@@ -15,7 +15,7 @@ LIGO types are built on top of Michelson's type system.
 
 ## Built-in types
 
-For quick reference, you can find all the built-in types [here](https://gitlab.com/ligolang/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
+For quick reference, you can find all the built-in types [here](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
 
 ## Type aliases
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/reference/toplevel.md b/gitlab-pages/website/versioned_docs/version-1.2.0/reference/toplevel.md
index 11fcacd0ad..ef30018f61 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/reference/toplevel.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/reference/toplevel.md
@@ -382,8 +382,8 @@ type 'v ticket
 </SyntaxTitle>
 
 Edo protocol introduced the following ticket type.
-Follow this [wallet example](https://gitlab.com/ligolang/ligo/-/blob/dev/src/test/contracts/ticket_wallet.mligo) for an example of
-correct usage (it goes with its [builder](https://gitlab.com/ligolang/ligo/-/blob/dev/src/test/contracts/ticket_builder.mligo)).
+Follow this [wallet example](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/test/contracts/ticket_wallet.mligo) for an example of
+correct usage (it goes with its [builder](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/test/contracts/ticket_builder.mligo)).
 This [article](https://medium.com/tezos-israel/tickets-on-edo-simply-explained-c5a411cc27f9) might also be useful.
 
 Note that a variable containing a ticket can only be used once (they are not `DUP`-able).
diff --git a/gitlab-pages/website/versioned_docs/version-1.2.0/tutorials/inter-contract-calls/inter-contract-calls.md b/gitlab-pages/website/versioned_docs/version-1.2.0/tutorials/inter-contract-calls/inter-contract-calls.md
index c40660e7ad..3dddc537f9 100644
--- a/gitlab-pages/website/versioned_docs/version-1.2.0/tutorials/inter-contract-calls/inter-contract-calls.md
+++ b/gitlab-pages/website/versioned_docs/version-1.2.0/tutorials/inter-contract-calls/inter-contract-calls.md
@@ -278,7 +278,7 @@ let iswhitelisted (arg : address * (bool contract)) (s : storage) : operation li
 </Syntax>
 
 
-Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/ligolang/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
+Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/mavryk-network/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
 
 <Syntax syntax="cameligo">
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/documentation-and-releases.md b/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/documentation-and-releases.md
index 2c3199a15d..1a5cb8f357 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/documentation-and-releases.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/documentation-and-releases.md
@@ -46,4 +46,4 @@ Development releases of LIGO are tagged `next` and are built with each commit to
 
 ### Stable releases
 
-Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/ligolang/ligo/-/releases and pushing images to docker.
+Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/mavryk-network/ligo/-/releases and pushing images to docker.
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/ligo_test_guide.md b/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/ligo_test_guide.md
index f5b3b0942d..0fee487366 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/ligo_test_guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/contributors/ligo_test_guide.md
@@ -7,9 +7,9 @@ Bonus: you will become more familiar with LIGO in the process!
 Tests are written in OCaml, as LIGO doesn't (yet) have a good way to do automated testing. Thankfully the test code is typically less demanding than the features being tested.
 
 Tests are currently contained in
-[src/test](https://gitlab.com/ligolang/ligo/tree/dev/src/test), but
+[src/test](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test), but
 most are integration tests which rely on test contracts kept in
-[src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts). If
+[src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts). If
 you are new to LIGO, reading these contracts can be a useful
 introduction to a particular LIGO syntax.
 
@@ -34,7 +34,7 @@ LIGO is divided into two parts
 - the **front end** handles syntax
 - the **backend** optimises and compiles a core language shared between syntaxes
 
-You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/ligolang/ligo/tree/dev/src/passes/01-parsing).
+You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/mavryk-network/ligo/tree/dev/src/passes/01-parsing).
 
 ### Two Useful Test Cases Using LIGO
 
@@ -65,9 +65,9 @@ a useful supplement to human testing.
 LIGO's OCaml-based tests are written in
 [alcotest](https://github.com/mirage/alcotest/). However, the tests
 you encounter in
-[src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml)
+[src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml)
 are built on top of some abstractions, currently defined in
-[src/test/test_helpers.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/test_helpers.ml). The
+[src/test/test_helpers.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/test_helpers.ml). The
 use of these can be inferred fairly well from looking at existing
 tests, but let us break a few of them down for analysis.
 
@@ -136,7 +136,7 @@ convert our expected test values into LIGO expressions and
 data. Constructors such as `e_list` and `e_address` provide a bridge
 between LIGO and OCaml. Their definitions can be found in files such
 as
-[src/stages/ast_core/combinators.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/stages/ast_core/combinators.ml),
+[src/stages/ast_core/combinators.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/stages/ast_core/combinators.ml),
 or using
 [Merlin's definition point finder](https://github.com/ocaml/merlin/wiki). These
 same functions are used during the simplification stage of LIGO
@@ -149,8 +149,8 @@ What if we want to write a test of our own? If the test is in the
 integration test vein (which it probably is if you are testing new
 syntax or features), then the process looks something like:
 
-1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts).
-2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
+1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts).
+2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
 3. Write the feature, assuming it does not already exist. Build the
    resulting version of LIGO without errors.
 4. Run the test suite, see if your test(s) pass. If they do, you are
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/demo/ligo-snippet.md b/gitlab-pages/website/versioned_docs/version-1.3.0/demo/ligo-snippet.md
index fd924cfeb7..8c57550b72 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/demo/ligo-snippet.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/demo/ligo-snippet.md
@@ -6,7 +6,7 @@ title: LIGO snippets Demo
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-“ligo-snippets” (https://www.npmjs.com/package/@ligolang/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
+“ligo-snippets” (https://www.npmjs.com/package/@mavryk-network/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
 
 The user will see LIGO code with syntax highlighting, and an action button allowing the user to open the source code in the LIGO Web IDE (https://ide.ligolang.org).
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/faq/v1-migration-guide.md b/gitlab-pages/website/versioned_docs/version-1.3.0/faq/v1-migration-guide.md
index 593e60720b..57f69d37f7 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/faq/v1-migration-guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/faq/v1-migration-guide.md
@@ -26,12 +26,12 @@ Another consequence of this change is that, when originating a contract for test
 We are also rolling out a new feature allowing the addition, removal and update of dynamic entry points for a contract after deployment. This could be a useful feature for example when building a DAO which allows on-chain vote to upgrade its code (or a DAO which controls the code of another separate contract). For more information, see [the documentation](../advanced/dynamic-entrypoints.md) and [the reference](../reference/dynamic_entrypoints.md) for this feature.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2818
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2814
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2810
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2805
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2831
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2885
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2818
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2814
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2810
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2805
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2831
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2885
 
 #### Uniform calling convention for views and entry points.
 
@@ -84,11 +84,11 @@ const get_storage = (_: unit, storage: int): int => storage
 
 #### `contract_of` and `parameter_of`
 
-The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
+The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2685
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2685
 
 ### `export` and `@private` now have the expected effect
 
@@ -109,8 +109,8 @@ const y = Foo.Bar.x
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2796
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2796
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
 
 ### The comb layout is now used by default
 
@@ -125,7 +125,7 @@ If your project has a stable ABI that other tools rely on, you might need to man
 Once reaching the optimization phase of your development process, youu may wish to try annotating large variants (which contain many cases) with `@layout("tree")` / `[@layout tree]` and comparing the size and gas consumption of the compiled contracts.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/1816.
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/1816.
 
 ### A small set of annotations / decorators are now supported
 
@@ -159,11 +159,11 @@ There are also two internal annotations / decorators, which should not appear in
 * `@hidden`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/ligolang/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
 
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
 
 ### Field and tuple component access
 
@@ -178,14 +178,14 @@ const stuff = {
 const part : bool = stuff.y["universe"][2];
 ```
 
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Miscellaneous
 
-* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2690.
-* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/ligolang/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/ligolang/ligo/-/merge_requests/2455 and https://gitlab.com/ligolang/ligo/-/merge_requests/2607.
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2501
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2500
+* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2690.
+* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2455 and https://gitlab.com/mavryk-network/ligo/-/merge_requests/2607.
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2501
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2500
 
 ## JsLIGO
 
@@ -194,8 +194,8 @@ const part : bool = stuff.y["universe"][2];
 You can now write `3mav` or `3mumav` instead of `3 as mav` or `3 as mumav`. This convenient feature was already present in CameLIGO and is now available in JsLIGO too!
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2853
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2853
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### New bitwise operators
 
@@ -227,7 +227,7 @@ const zero_bytes : bytes = 0x01 >> 1n
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Changes to pattern matching
 
@@ -296,7 +296,7 @@ Furthermore, there are a few changes to how patterns are written:
 * Patterns with one variable per parameter are written as expected: `Foo: (a, b) => a + b` becomes `when(Foo(a, b)): a + b`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 
 ### `_` is now a valid variable name and can't be used for its former throw-away semantics
@@ -331,7 +331,7 @@ const f = () => {
 If multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript. However, it is still possible to shadow a `_` within a smaller scope, e.g. if `_` is globally defined as an alias for another module, a function can still specify `_` as an argument name and shadow the global definition, which could cause issues. It is wise to skim over existing code for such cases.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2674
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2674
 
 ### Imports are now automatically re-exported
 
@@ -340,11 +340,11 @@ When a module is imported e.g. with `#import "foo.jsligo" "Foo"` inside the file
 For example, a third file importing `bar.jsligo` as `Bar` can write `Bar.Foo.x` to access the `x` defined in `foo.jsligo`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2815
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2815
 
 ### Miscellaneous
 
-* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ## CameLIGO
 
@@ -362,7 +362,7 @@ let part : bool = stuff.y.2.universe
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Package management: use ligo.json instead of package.json or esy.json
 
@@ -371,8 +371,8 @@ Users often work with JaveScript toolchain alongside ours. Using package.json to
 As part of this change, we are no longer using the `esy` tool for package management, and the `installation.json` file, formerly located at `_esy/ligo/installation.json`, should now be moved to `_ligo/ligo/installation.json`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2817
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2785
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2883
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2817
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2785
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2883
 
 <!-- updated use of entry -->
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/editor-support.md b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/editor-support.md
index 8b63670043..fd5caca6ff 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/editor-support.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/editor-support.md
@@ -7,8 +7,8 @@ Painters need a brush and a canvas. Developers need a good IDE experience. LIGO
 
 - **[Install the LIGO extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)**
 
-- **[Install the LIGO extension for VIM](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
+- **[Install the LIGO extension for VIM](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
 
-- **[Install the LIGO extension for Emacs](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/emacs/README.md)**
+- **[Install the LIGO extension for Emacs](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/emacs/README.md)**
 
 <!-- updated use of entry -->
\ No newline at end of file
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/installation.md b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/installation.md
index 2355af16e9..8d298214e7 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/installation.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/installation.md
@@ -14,7 +14,7 @@ You can also try LIGO in a Gitpod environment
 
 ## Releases
 
-Releases are available at the [releases page of GitLab project](https://gitlab.com/ligolang/ligo/-/releases). All the artifacts are attached there.
+Releases are available at the [releases page of GitLab project](https://gitlab.com/mavryk-network/ligo/-/releases). All the artifacts are attached there.
 
 If you wish to see the changelog, you can either run `ligo changelog` or go to [this page](https://ligolang.org/docs/next/intro/changelog). It contains links to corresponding releases, should you wish to download the artifacts.
 
@@ -33,14 +33,14 @@ If you wish to see the changelog, you can either run `ligo changelog` or go to [
 
 The `ligo` executable is statically linked. It should run on most modern Linux distributions.
 
-You can get the rolling release [here](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
+You can get the rolling release [here](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
 
 ```zsh
-wget https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo
+wget https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo
 chmod +x ./ligo
 ```
 
-For a specific version, you can visit our [release page](https://gitlab.com/ligolang/ligo/-/releases/).  
+For a specific version, you can visit our [release page](https://gitlab.com/mavryk-network/ligo/-/releases/).  
 Optionally, you can put it somewhere in your `PATH` for easy access:
 
 ```zsh
@@ -52,22 +52,22 @@ sudo cp ./ligo /usr/local/bin
 Try our tap :
 
 ```bash
-brew tap ligolang/ligo https://gitlab.com/ligolang/ligo.git
-brew install ligolang/ligo/ligo
+brew tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git
+brew install mavryk-network/ligo/ligo
 ```
 
 To upgrade ligo :
 
 ```bash
 brew update
-brew upgrade ligolang/ligo/ligo
+brew upgrade mavryk-network/ligo/ligo
 ```
 
 </TabItem>
 <TabItem value="deb">
 
 A `.deb` package containing the static `ligo` executable is also available.
-First, download [the package](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
+First, download [the package](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
 
 ```zsh
 sudo apt install ./ligo.deb
@@ -96,18 +96,18 @@ If you've [installed 🐳 Docker](https://docs.docker.com/install/), you can run
 
 Linux or OSX:
 > ```sh
-> docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0
+> docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0
 > ```
 > For convenience you can alias the above command
 > ```sh
-> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0'
+> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0'
 > ```
 > To make this `alias` persistent across terminal sessions you need to configure your shell.     
 > Here is a [good link](https://www.tecmint.com/create-alias-in-linux/) with the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 <TabItem value="windows">
@@ -115,18 +115,18 @@ Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/l
 It's possible to use ligo in [Docker](https://docs.docker.com/install/) through docker or [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install)
 
 > ```dos
-> docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0`
+> docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0`
 > ```
 > For convenience you can alias the above command
 > ```dos
-> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0 $*
+> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0 $*
 > ```
 > To make the alias persistent across terminal sessions you need to add the `doskey` to the Windows Registry.  
 > Follow [this stackoverflow answer](https://stackoverflow.com/a/21040825) for the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 </Tabs>
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/ligo-intro.md b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/ligo-intro.md
index 251bc0b000..91da7a7075 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/intro/ligo-intro.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/intro/ligo-intro.md
@@ -84,7 +84,7 @@ For critical code, LIGO also keeps its compiled output unbloated making **possib
   [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Understand and troubleshoot your code with the debugger available in [vscode extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Integrate LIGO to your pipeline with [ligo github action](https://github.com/marigold-dev/ligo-action)
-- Test your documentation with [ligo-mdx](https://github.com/ligolang/ligo-mdx)
+- Test your documentation with [ligo-mdx](https://github.com/mavryk-network/ligo-mdx)
 
 ---
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/language-basics/types.md b/gitlab-pages/website/versioned_docs/version-1.3.0/language-basics/types.md
index e6c1e5a2e2..ddcdc3044b 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/language-basics/types.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/language-basics/types.md
@@ -15,7 +15,7 @@ LIGO types are built on top of Michelson's type system.
 
 ## Built-in types
 
-For quick reference, you can find all the built-in types [here](https://gitlab.com/ligolang/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
+For quick reference, you can find all the built-in types [here](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
 
 ## Type aliases
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/reference/toplevel.md b/gitlab-pages/website/versioned_docs/version-1.3.0/reference/toplevel.md
index 926fd53a6f..729e6ad21d 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/reference/toplevel.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/reference/toplevel.md
@@ -402,8 +402,8 @@ type 'v ticket
 </SyntaxTitle>
 
 Edo protocol introduced the following ticket type.
-Follow this [wallet example](https://gitlab.com/ligolang/ligo/-/blob/dev/src/test/contracts/ticket_wallet.mligo) for an example of
-correct usage (it goes with its [builder](https://gitlab.com/ligolang/ligo/-/blob/dev/src/test/contracts/ticket_builder.mligo)).
+Follow this [wallet example](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/test/contracts/ticket_wallet.mligo) for an example of
+correct usage (it goes with its [builder](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/test/contracts/ticket_builder.mligo)).
 This [article](https://medium.com/tezos-israel/tickets-on-edo-simply-explained-c5a411cc27f9) might also be useful.
 
 Note that a variable containing a ticket can only be used once (they are not `DUP`-able).
diff --git a/gitlab-pages/website/versioned_docs/version-1.3.0/tutorials/inter-contract-calls/inter-contract-calls.md b/gitlab-pages/website/versioned_docs/version-1.3.0/tutorials/inter-contract-calls/inter-contract-calls.md
index c40660e7ad..3dddc537f9 100644
--- a/gitlab-pages/website/versioned_docs/version-1.3.0/tutorials/inter-contract-calls/inter-contract-calls.md
+++ b/gitlab-pages/website/versioned_docs/version-1.3.0/tutorials/inter-contract-calls/inter-contract-calls.md
@@ -278,7 +278,7 @@ let iswhitelisted (arg : address * (bool contract)) (s : storage) : operation li
 </Syntax>
 
 
-Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/ligolang/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
+Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/mavryk-network/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
 
 <Syntax syntax="cameligo">
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/documentation-and-releases.md b/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/documentation-and-releases.md
index 2c3199a15d..1a5cb8f357 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/documentation-and-releases.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/documentation-and-releases.md
@@ -46,4 +46,4 @@ Development releases of LIGO are tagged `next` and are built with each commit to
 
 ### Stable releases
 
-Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/ligolang/ligo/-/releases and pushing images to docker.
+Stable releases are tags of form `x.x.x`, generally sticking to semver conventions. Such tags are automatically built on CI, producing a release in https://gitlab.com/mavryk-network/ligo/-/releases and pushing images to docker.
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/ligo_test_guide.md b/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/ligo_test_guide.md
index f5b3b0942d..0fee487366 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/ligo_test_guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/contributors/ligo_test_guide.md
@@ -7,9 +7,9 @@ Bonus: you will become more familiar with LIGO in the process!
 Tests are written in OCaml, as LIGO doesn't (yet) have a good way to do automated testing. Thankfully the test code is typically less demanding than the features being tested.
 
 Tests are currently contained in
-[src/test](https://gitlab.com/ligolang/ligo/tree/dev/src/test), but
+[src/test](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test), but
 most are integration tests which rely on test contracts kept in
-[src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts). If
+[src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts). If
 you are new to LIGO, reading these contracts can be a useful
 introduction to a particular LIGO syntax.
 
@@ -34,7 +34,7 @@ LIGO is divided into two parts
 - the **front end** handles syntax
 - the **backend** optimises and compiles a core language shared between syntaxes
 
-You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/ligolang/ligo/tree/dev/src/passes/01-parsing).
+You can find basic test cases for a particular LIGO syntax by studying its parser. You will find the parser under [src/passes/1-parser](https://gitlab.com/mavryk-network/ligo/tree/dev/src/passes/01-parsing).
 
 ### Two Useful Test Cases Using LIGO
 
@@ -65,9 +65,9 @@ a useful supplement to human testing.
 LIGO's OCaml-based tests are written in
 [alcotest](https://github.com/mirage/alcotest/). However, the tests
 you encounter in
-[src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml)
+[src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml)
 are built on top of some abstractions, currently defined in
-[src/test/test_helpers.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/test_helpers.ml). The
+[src/test/test_helpers.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/test_helpers.ml). The
 use of these can be inferred fairly well from looking at existing
 tests, but let us break a few of them down for analysis.
 
@@ -136,7 +136,7 @@ convert our expected test values into LIGO expressions and
 data. Constructors such as `e_list` and `e_address` provide a bridge
 between LIGO and OCaml. Their definitions can be found in files such
 as
-[src/stages/ast_core/combinators.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/stages/ast_core/combinators.ml),
+[src/stages/ast_core/combinators.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/stages/ast_core/combinators.ml),
 or using
 [Merlin's definition point finder](https://github.com/ocaml/merlin/wiki). These
 same functions are used during the simplification stage of LIGO
@@ -149,8 +149,8 @@ What if we want to write a test of our own? If the test is in the
 integration test vein (which it probably is if you are testing new
 syntax or features), then the process looks something like:
 
-1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/ligolang/ligo/tree/dev/src/test/contracts).
-2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/ligolang/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
+1. Write a test contract which uses the new syntax or feature in [src/test/contracts](https://gitlab.com/mavryk-network/ligo/tree/dev/src/test/contracts).
+2. Write an integration test in [src/test/integration_tests.ml](https://gitlab.com/mavryk-network/ligo/blob/dev/src/test/integration_tests.ml) in the vein of existing tests, make sure you add it to the test runner that is currently located at the bottom of the file.
 3. Write the feature, assuming it does not already exist. Build the
    resulting version of LIGO without errors.
 4. Run the test suite, see if your test(s) pass. If they do, you are
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/demo/ligo-snippet.md b/gitlab-pages/website/versioned_docs/version-1.4.0/demo/ligo-snippet.md
index fd924cfeb7..8c57550b72 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/demo/ligo-snippet.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/demo/ligo-snippet.md
@@ -6,7 +6,7 @@ title: LIGO snippets Demo
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-“ligo-snippets” (https://www.npmjs.com/package/@ligolang/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
+“ligo-snippets” (https://www.npmjs.com/package/@mavryk-network/ligo-snippets) is a React component that can be included on any webpage to display LIGO source code to users.
 
 The user will see LIGO code with syntax highlighting, and an action button allowing the user to open the source code in the LIGO Web IDE (https://ide.ligolang.org).
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/faq/v1-migration-guide.md b/gitlab-pages/website/versioned_docs/version-1.4.0/faq/v1-migration-guide.md
index 01c343ff0a..48abc29470 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/faq/v1-migration-guide.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/faq/v1-migration-guide.md
@@ -26,12 +26,12 @@ Another consequence of this change is that, when originating a contract for test
 We are also rolling out a new feature allowing the addition, removal and update of dynamic entry points for a contract after deployment. This could be a useful feature for example when building a DAO which allows on-chain vote to upgrade its code (or a DAO which controls the code of another separate contract). For more information, see [the documentation](../advanced/dynamic-entrypoints.md) and [the reference](../reference/Dynamic_entrypoints.md) for this feature.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2818
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2814
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2810
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2805
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2831
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2885
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2818
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2814
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2810
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2805
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2831
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2885
 
 #### Uniform calling convention for views and entry points.
 
@@ -84,11 +84,11 @@ const get_storage = (_: unit, storage: int): int => storage
 
 #### `contract_of` and `parameter_of`
 
-The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
+The aforementioned changes to `@entry` and the `main` function have affected how contracts are tested, starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)). See [the documentation on testing](../advanced/testing.md#testing-a-contract-declared-as-a-module-or-namespace) for examples on how to use `contract_of` and `parameter_of`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2685
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2685
 
 ### `export` and `@private` now have the expected effect
 
@@ -109,8 +109,8 @@ const y = Foo.Bar.x
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2796
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2796
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2684 in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690))
 
 ### The comb layout is now used by default
 
@@ -125,7 +125,7 @@ If your project has a stable ABI that other tools rely on, you might need to man
 Once reaching the optimization phase of your development process, youu may wish to try annotating large variants (which contain many cases) with `@layout("tree")` / `[@layout tree]` and comparing the size and gas consumption of the compiled contracts.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/1816.
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/1816.
 
 ### A small set of annotations / decorators are now supported
 
@@ -159,11 +159,11 @@ There are also two internal annotations / decorators, which should not appear in
 * `@hidden`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/ligolang/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2619 in [v0.67.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.67.0) ([changelog](../intro/changelog.md#0670))
 
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2476
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2476
 
 ### Field and tuple component access
 
@@ -178,14 +178,14 @@ const stuff = {
 const part : bool = stuff.y["universe"][2];
 ```
 
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Miscellaneous
 
-* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/ligolang/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2690.
-* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/ligolang/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/ligolang/ligo/-/merge_requests/2455 and https://gitlab.com/ligolang/ligo/-/merge_requests/2607.
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2501
-* Starting from [v0.64.2](https://gitlab.com/ligolang/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/ligolang/ligo/-/merge_requests/2500
+* The internal command `ligo daemon` has been removed in [v0.69.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.69.0) ([changelog](../intro/changelog.md#0690)). It was previously used by the old language server to create a persistent LIGO process, but it was hacky and offered no performance improvements. There should be no noticeable change for the user, as the new language server (used e.g. by the VsCode plug-in) does not make use of this command anymore. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2690.
+* The support for CST mutation testing has been dropped in [v0.66.0](https://gitlab.com/mavryk-network/ligo/-/releases/0.66.0) ([changelog](../intro/changelog.md#0660)). Unfortunately, that feature was incomplete and broken. With the disappearance of this feature, the command `ligo mutate` has been removed. However, AST mutation testing is still supported and part of the [testing framework](../advanced/mutation-testing.md). MRs: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2455 and https://gitlab.com/mavryk-network/ligo/-/merge_requests/2607.
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the transpilation commands now take `--from-syntax` and `--to-syntax`, instead of the former, less clear use of `--syntax` for the source syntax and an unnamed parameter for the destination syntax. The destination syntax can still be inferred from the filename given to `-o`, e.g. `-o dest.jsligo`. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2501
+* Starting from [v0.64.2](https://gitlab.com/mavryk-network/ligo/-/releases/0.64.2) ([changelog](../intro/changelog.md#0642)), the Kathmandu protocol is deprecated. If you need to recompile an old LIGO contract for an outdated protocol version, you may use the compiler version that the project was developed with. MR: https://gitlab.com/mavryk-network/ligo/-/merge_requests/2500
 
 ## JsLIGO
 
@@ -194,8 +194,8 @@ const part : bool = stuff.y["universe"][2];
 You can now write `3mav` or `3mumav` instead of `3 as mav` or `3 as mumav`. This convenient feature was already present in CameLIGO and is now available in JsLIGO too!
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2853
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2853
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### New bitwise operators
 
@@ -227,7 +227,7 @@ const zero_bytes : bytes = 0x01 >> 1n
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Changes to pattern matching
 
@@ -296,7 +296,7 @@ Furthermore, there are a few changes to how patterns are written:
 * Patterns with one variable per parameter are written as expected: `Foo: (a, b) => a + b` becomes `when(Foo(a, b)): a + b`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 
 ### `_` is now a valid variable name and can't be used for its former throw-away semantics
@@ -331,7 +331,7 @@ const f = () => {
 If multiple _ variable are bound in the same scope, it will result in an error (duplicate block-scoped variable) just as in TypeScript. However, it is still possible to shadow a `_` within a smaller scope, e.g. if `_` is globally defined as an alias for another module, a function can still specify `_` as an argument name and shadow the global definition, which could cause issues. It is wise to skim over existing code for such cases.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2674
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2674
 
 ### Imports are now automatically re-exported
 
@@ -340,11 +340,11 @@ When a module is imported e.g. with `#import "foo.jsligo" "Foo"` inside the file
 For example, a third file importing `bar.jsligo` as `Bar` can write `Bar.Foo.x` to access the `x` defined in `foo.jsligo`
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2815
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2815
 
 ### Miscellaneous
 
-* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* `true` and `false` are now keywords (not variables), and cannot be shadowed by a local variable declaration. https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ## CameLIGO
 
@@ -362,7 +362,7 @@ let part : bool = stuff.y.2.universe
 ```
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2661
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2661
 
 ### Package management: use ligo.json instead of package.json or esy.json
 
@@ -371,8 +371,8 @@ Users often work with JaveScript toolchain alongside ours. Using package.json to
 As part of this change, we are no longer using the `esy` tool for package management, and the `installation.json` file, formerly located at `_esy/ligo/installation.json`, should now be moved to `_ligo/ligo/installation.json`.
 
 MRs:
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2817
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2785
-* https://gitlab.com/ligolang/ligo/-/merge_requests/2883
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2817
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2785
+* https://gitlab.com/mavryk-network/ligo/-/merge_requests/2883
 
 <!-- updated use of entry -->
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/editor-support.md b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/editor-support.md
index 8b63670043..fd5caca6ff 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/editor-support.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/editor-support.md
@@ -7,8 +7,8 @@ Painters need a brush and a canvas. Developers need a good IDE experience. LIGO
 
 - **[Install the LIGO extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)**
 
-- **[Install the LIGO extension for VIM](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
+- **[Install the LIGO extension for VIM](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vim/ligo/start/ligo/README.md)**
 
-- **[Install the LIGO extension for Emacs](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/emacs/README.md)**
+- **[Install the LIGO extension for Emacs](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/emacs/README.md)**
 
 <!-- updated use of entry -->
\ No newline at end of file
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/installation.md b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/installation.md
index 2355af16e9..8d298214e7 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/installation.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/installation.md
@@ -14,7 +14,7 @@ You can also try LIGO in a Gitpod environment
 
 ## Releases
 
-Releases are available at the [releases page of GitLab project](https://gitlab.com/ligolang/ligo/-/releases). All the artifacts are attached there.
+Releases are available at the [releases page of GitLab project](https://gitlab.com/mavryk-network/ligo/-/releases). All the artifacts are attached there.
 
 If you wish to see the changelog, you can either run `ligo changelog` or go to [this page](https://ligolang.org/docs/next/intro/changelog). It contains links to corresponding releases, should you wish to download the artifacts.
 
@@ -33,14 +33,14 @@ If you wish to see the changelog, you can either run `ligo changelog` or go to [
 
 The `ligo` executable is statically linked. It should run on most modern Linux distributions.
 
-You can get the rolling release [here](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
+You can get the rolling release [here](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo), make it executable, and you are done!
 
 ```zsh
-wget https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo
+wget https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo
 chmod +x ./ligo
 ```
 
-For a specific version, you can visit our [release page](https://gitlab.com/ligolang/ligo/-/releases/).  
+For a specific version, you can visit our [release page](https://gitlab.com/mavryk-network/ligo/-/releases/).  
 Optionally, you can put it somewhere in your `PATH` for easy access:
 
 ```zsh
@@ -52,22 +52,22 @@ sudo cp ./ligo /usr/local/bin
 Try our tap :
 
 ```bash
-brew tap ligolang/ligo https://gitlab.com/ligolang/ligo.git
-brew install ligolang/ligo/ligo
+brew tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git
+brew install mavryk-network/ligo/ligo
 ```
 
 To upgrade ligo :
 
 ```bash
 brew update
-brew upgrade ligolang/ligo/ligo
+brew upgrade mavryk-network/ligo/ligo
 ```
 
 </TabItem>
 <TabItem value="deb">
 
 A `.deb` package containing the static `ligo` executable is also available.
-First, download [the package](https://gitlab.com/ligolang/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
+First, download [the package](https://gitlab.com/mavryk-network/ligo/-/jobs/6303579494/artifacts/raw/ligo.deb), and then install using: 
 
 ```zsh
 sudo apt install ./ligo.deb
@@ -96,18 +96,18 @@ If you've [installed 🐳 Docker](https://docs.docker.com/install/), you can run
 
 Linux or OSX:
 > ```sh
-> docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0
+> docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0
 > ```
 > For convenience you can alias the above command
 > ```sh
-> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:1.4.0'
+> alias ligo='docker run --rm -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:1.4.0'
 > ```
 > To make this `alias` persistent across terminal sessions you need to configure your shell.     
 > Here is a [good link](https://www.tecmint.com/create-alias-in-linux/) with the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 <TabItem value="windows">
@@ -115,18 +115,18 @@ Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/l
 It's possible to use ligo in [Docker](https://docs.docker.com/install/) through docker or [WSL2](https://learn.microsoft.com/en-us/windows/wsl/install)
 
 > ```dos
-> docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0`
+> docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0`
 > ```
 > For convenience you can alias the above command
 > ```dos
-> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd ligolang/ligo:1.4.0 $*
+> doskey ligo=docker run --rm -v "%CD%":/cd -w /cd mavrykdynamics/ligo:1.4.0 $*
 > ```
 > To make the alias persistent across terminal sessions you need to add the `doskey` to the Windows Registry.  
 > Follow [this stackoverflow answer](https://stackoverflow.com/a/21040825) for the steps on how to do that.
 
 Or if you want the development version, replace the version above with `next`.
 
-Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/ligolang/ligo/tags).
+Or run one of the older versions found on [DockerHub](https://hub.docker.com/r/mavryk-network/ligo/tags).
 
 </TabItem>
 </Tabs>
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/ligo-intro.md b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/ligo-intro.md
index 251bc0b000..91da7a7075 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/intro/ligo-intro.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/intro/ligo-intro.md
@@ -84,7 +84,7 @@ For critical code, LIGO also keeps its compiled output unbloated making **possib
   [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Understand and troubleshoot your code with the debugger available in [vscode extension](https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode)
 - Integrate LIGO to your pipeline with [ligo github action](https://github.com/marigold-dev/ligo-action)
-- Test your documentation with [ligo-mdx](https://github.com/ligolang/ligo-mdx)
+- Test your documentation with [ligo-mdx](https://github.com/mavryk-network/ligo-mdx)
 
 ---
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/language-basics/types.md b/gitlab-pages/website/versioned_docs/version-1.4.0/language-basics/types.md
index e6c1e5a2e2..ddcdc3044b 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/language-basics/types.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/language-basics/types.md
@@ -15,7 +15,7 @@ LIGO types are built on top of Michelson's type system.
 
 ## Built-in types
 
-For quick reference, you can find all the built-in types [here](https://gitlab.com/ligolang/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
+For quick reference, you can find all the built-in types [here](https://gitlab.com/mavryk-network/ligo/-/blob/dev/src/main/build/ligo_lib/std_lib.mligo#L1-33).
 
 ## Type aliases
 
diff --git a/gitlab-pages/website/versioned_docs/version-1.4.0/tutorials/inter-contract-calls/inter-contract-calls.md b/gitlab-pages/website/versioned_docs/version-1.4.0/tutorials/inter-contract-calls/inter-contract-calls.md
index c40660e7ad..3dddc537f9 100644
--- a/gitlab-pages/website/versioned_docs/version-1.4.0/tutorials/inter-contract-calls/inter-contract-calls.md
+++ b/gitlab-pages/website/versioned_docs/version-1.4.0/tutorials/inter-contract-calls/inter-contract-calls.md
@@ -278,7 +278,7 @@ let iswhitelisted (arg : address * (bool contract)) (s : storage) : operation li
 </Syntax>
 
 
-Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/ligolang/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
+Now imagine we want to control a contract with the following interface (we omit the full code of the contract for clarity; you can find it in the [examples folder](https://gitlab.com/mavryk-network/ligo/-/tree/dev/gitlab-pages/docs/tutorials/inter-contract-calls/examples)):
 
 <Syntax syntax="cameligo">
 
diff --git a/scripts/build_docker_image.sh b/scripts/build_docker_image.sh
index b39bdc22a6..ae83de1c12 100755
--- a/scripts/build_docker_image.sh
+++ b/scripts/build_docker_image.sh
@@ -7,4 +7,4 @@ if test $# -ne 1 || test "x$1" = "-h" -o "x$1" = "x--help"; then
   exit 1
 fi
 
-docker build -t "${LIGO_REGISTRY_IMAGE_BUILD:-ligolang/ligo}:$1" -f ./docker/distribution/debian/distribute.Dockerfile .
+docker build -t "${LIGO_REGISTRY_IMAGE_BUILD:-mavrykdynamics/ligo}:$1" -f ./docker/distribution/debian/distribute.Dockerfile .
diff --git a/scripts/changelog.md.mustache b/scripts/changelog.md.mustache
index a8a1be00c5..0c4a13fc99 100644
--- a/scripts/changelog.md.mustache
+++ b/scripts/changelog.md.mustache
@@ -2,22 +2,22 @@
 
 {{#changelog}}
 {{#is_next}}
-## <ins>[{{{version}}}](https://gitlab.com/ligolang/ligo/-/commits/dev)</ins>
+## <ins>[{{{version}}}](https://gitlab.com/mavryk-network/ligo/-/commits/dev)</ins>
 {{/is_next}}
 {{^is_next}}
-## <ins>[{{{version}}}](https://gitlab.com/ligolang/ligo/-/releases/{{{version}}})</ins>
+## <ins>[{{{version}}}](https://gitlab.com/mavryk-network/ligo/-/releases/{{{version}}})</ins>
 {{/is_next}}
-> Run this release with Docker: `docker run ligolang/ligo:{{{version}}}`
+> Run this release with Docker: `docker run mavrykdynamics/ligo:{{{version}}}`
 
 {{#changes}}
 {{#breaking_ind}}
 ### Breaking :
 {{#breaking}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/breaking}}
@@ -26,11 +26,11 @@
 {{#added_ind}}
 ### Added :
 {{#added}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/added}}
@@ -39,11 +39,11 @@
 {{#fixed_ind}}
 ### Fixed :
 {{#fixed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/fixed}}
@@ -52,11 +52,11 @@
 {{#changed_ind}}
 ### Changed :
 {{#changed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/changed}}
@@ -65,11 +65,11 @@
 {{#deprecated_ind}}
 ### Deprecated :
 {{#deprecated}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/deprecated}}
@@ -78,11 +78,11 @@
 {{#removed_ind}}
 ### Removed :
 {{#removed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/removed}}
@@ -91,11 +91,11 @@
 {{#performance_ind}}
 ### Performance :
 {{#performance}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/performance}}
@@ -104,11 +104,11 @@
 {{#internal_ind}}
 ### Internal :
 {{#internal}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/internal}}
@@ -117,11 +117,11 @@
 {{#other_ind}}
 ### Other :
 {{#other}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/other}}
@@ -130,11 +130,11 @@
 {{#null_ind}}
 ### Uncategorized :
 {{#null}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
   <details>
   <summary> <ins>Details</ins> : </summary>
   
-  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}){{/description}}
+  {{#description}}{{{description}}}{{/description}}{{^description}}No details provided for this change. Please visit the [MR to learn more](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}){{/description}}
   
   </details>
 {{/null}}
@@ -148,4 +148,4 @@ _No changes for this version_
 
 {{/changelog}}
 
-For older version, please visit https://gitlab.com/ligolang/ligo/-/releasessla
+For older version, please visit https://gitlab.com/mavryk-network/ligo/-/releasessla
diff --git a/scripts/changelog.txt.mustache b/scripts/changelog.txt.mustache
index a2125403e2..a38aef3200 100644
--- a/scripts/changelog.txt.mustache
+++ b/scripts/changelog.txt.mustache
@@ -2,81 +2,81 @@
 
 {{#changelog}}
 {{#is_next}}
-## <ins>[{{{version}}}](https://gitlab.com/ligolang/ligo/-/commits/dev)</ins>
+## <ins>[{{{version}}}](https://gitlab.com/mavryk-network/ligo/-/commits/dev)</ins>
 {{/is_next}}
 {{^is_next}}
-## <ins>[{{{version}}}](https://gitlab.com/ligolang/ligo/-/releases/{{{version}}})</ins>
+## <ins>[{{{version}}}](https://gitlab.com/mavryk-network/ligo/-/releases/{{{version}}})</ins>
 {{/is_next}}
-> Run this release with Docker: `docker run ligolang/ligo:{{{version}}}`
+> Run this release with Docker: `docker run mavrykdynamics/ligo:{{{version}}}`
 
 {{#changes}}
 {{#breaking_ind}}
 ### Breaking :
 {{#breaking}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/breaking}}
 {{/breaking_ind}}
 
 {{#added_ind}}
 ### Added :
 {{#added}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/added}}
 {{/added_ind}}
 
 {{#fixed_ind}}
 ### Fixed :
 {{#fixed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/fixed}}
 {{/fixed_ind}}
 
 {{#changed_ind}}
 ### Changed :
 {{#changed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/changed}}
 {{/changed_ind}}
 
 {{#deprecated_ind}}
 ### Deprecated :
 {{#deprecated}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/deprecated}}
 {{/deprecated_ind}}
 
 {{#removed_ind}}
 ### Removed :
 {{#removed}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/removed}}
 {{/removed_ind}}
 
 {{#performance_ind}}
 ### Performance :
 {{#performance}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/performance}}
 {{/performance_ind}}
 
 {{#internal_ind}}
 ### Internal :
 {{#internal}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/internal}}
 {{/internal_ind}}
 
 {{#other_ind}}
 ### Other :
 {{#other}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/other}}
 {{/other_ind}}
 
 {{#null_ind}}
 ### Uncategorized :
 {{#null}}
-* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/null}}
 {{/null_ind}}
 
diff --git a/scripts/distribution/generic/env_variables.sh b/scripts/distribution/generic/env_variables.sh
index a47629ae2b..ef8379a2e7 100755
--- a/scripts/distribution/generic/env_variables.sh
+++ b/scripts/distribution/generic/env_variables.sh
@@ -3,7 +3,7 @@
 # You can load the following variables using:
 # source ./scripts/distribution/generic/env_variables.sh
 
-export LIGO_REGISTRY_IMAGE_BASE_NAME="ligolang/ligo"
+export LIGO_REGISTRY_IMAGE_BASE_NAME="mavryk-network/ligo"
 # packages build locally are tagget by the 'short' commit hash,
 # instead of the build/job/pipeline ID as in the CI to avoid possible confusion
 # ligo_incrementing-id_commit-hash
diff --git a/scripts/install_build_environment.sh b/scripts/install_build_environment.sh
index 331a8f88f7..cf2a6c6665 100755
--- a/scripts/install_build_environment.sh
+++ b/scripts/install_build_environment.sh
@@ -82,7 +82,7 @@ else
         else
             echo "opam file hash doesn't match what was recorded at time of signature verification!"
             echo "(If you actually get this message, you should probably file an issue)"
-            echo "https://gitlab.com/ligolang/ligo/issues"
+            echo "https://gitlab.com/mavryk-network/ligo/issues"
             exit 1
         fi
     fi
diff --git a/scripts/installer.sh b/scripts/installer.sh
index 27d5f2270d..d5eb8f66f4 100644
--- a/scripts/installer.sh
+++ b/scripts/installer.sh
@@ -4,7 +4,7 @@ set -e
 # code quality: medium 2021-05-04
 
 # You can run this installer like this:
-# curl https://gitlab.com/ligolang/ligo/-/raw/dev/scripts/installer.sh | bash
+# curl https://gitlab.com/mavryk-network/ligo/-/raw/dev/scripts/installer.sh | bash
 # Make sure the marigold/ligo image is published at docker hub first
 
 # Check that we have one argument, that it contains only one line, and that it matches the regexp (next|[0-9.]*)
@@ -23,7 +23,7 @@ else
     echo "/usr/local/bin/ligo already exists and is a directory, cancelling installation"
   else
     # Pull the docker image used by ligo.sh
-    docker pull "ligolang/ligo:$version"
+    docker pull "mavrykdynamics/ligo:$version"
 
     sudo install -m 0755 /dev/stdin /usr/local/bin/ligo <<EOF
 #!/bin/sh
@@ -32,7 +32,7 @@ if test "x\$PWD" = "x"; then
   echo "Cannot detect the current directory, the environment variable PWD is empty."
   exit 1
 else
-  docker run --rm -v "\$PWD":"\$PWD" -w "\$PWD" ligolang/ligo:$version "\$@"
+  docker run --rm -v "\$PWD":"\$PWD" -w "\$PWD" mavrykdynamics/ligo:$version "\$@"
 fi
 EOF
   fi
diff --git a/scripts/ligo_ci.sh b/scripts/ligo_ci.sh
index a39da58738..0edda5f30c 100755
--- a/scripts/ligo_ci.sh
+++ b/scripts/ligo_ci.sh
@@ -1 +1 @@
-docker run -i -v "$PWD":"$PWD" -w "$PWD" ligolang/ligo:next "$@"
\ No newline at end of file
+docker run -i -v "$PWD":"$PWD" -w "$PWD" mavrykdynamics/ligo:next "$@"
\ No newline at end of file
diff --git a/scripts/list-to-dos.sh b/scripts/list-to-dos.sh
index 6bbe5a672b..27c9f17a3a 100755
--- a/scripts/list-to-dos.sh
+++ b/scripts/list-to-dos.sh
@@ -49,7 +49,7 @@ ignorecase() {
 }
 
 rea='s%^/(/(x3[0-9]/)*/)/(x3a.*/)/('"$(ignorecase 'to''do')"'/|'"$(ignorecase 'fix''me')"'/)/(.*/)$'
-rea="$rea"'%'"$(printf '<a href="https://gitlab.com/ligolang/ligo/-/blob/dev/' | to_hex)"
+rea="$rea"'%'"$(printf '<a href="https://gitlab.com/mavryk-network/ligo/-/blob/dev/' | to_hex)"
 reb="$(printf '#L' | to_hex)"'/1'"$(printf '">' | to_hex)"'/1/3'"$(printf '<strong>' | to_hex)"'/4'"$(printf '</strong>' | to_hex)"'/5'"$(printf '</a>' | to_hex)"
 reb="$reb"'%g'
 rea="$(printf '%s' "$rea" | tr '/' \\\\)"
@@ -63,7 +63,7 @@ for filehex in $(git ls-files -z | delimited_to_hex x00); do
   title_printed=false
   for matcheshex in $(grep -C 5 -i -n \\'(to''do'\\'|fix''me'\\')' -- "$file" | tr \\0 ' ' | to_hex | sed -e s/x0ax2dx2dx0a/\\n/g); do
     if test "$title_printed" = "false"; then
-      printf '%s' '<li><a href="https://gitlab.com/ligolang/ligo/-/blob/dev/'
+      printf '%s' '<li><a href="https://gitlab.com/mavryk-network/ligo/-/blob/dev/'
       printf '%s' "$file" | escapehtml
       printf '%s' '"><code>'
       printf '%s' "$file" | escapehtml
diff --git a/scripts/release-notes.md.mustache b/scripts/release-notes.md.mustache
index 0d5a0ac251..8594e447d9 100644
--- a/scripts/release-notes.md.mustache
+++ b/scripts/release-notes.md.mustache
@@ -2,43 +2,43 @@
 
 {{#changes}}
 {{#breaking}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/breaking}}
 
 {{#added}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/added}}
 
 {{#fixed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/fixed}}
 
 {{#changed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/changed}}
 
 {{#deprecated}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/deprecated}}
 
 {{#removed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/removed}}
 
 {{#performance}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/performance}}
 
 {{#internal}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/internal}}
 
 {{#other}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/other}}
 
 {{#null}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/null}}
 
 {{/changes}}
diff --git a/scripts/release-notes.txt.mustache b/scripts/release-notes.txt.mustache
index 0d5a0ac251..8594e447d9 100644
--- a/scripts/release-notes.txt.mustache
+++ b/scripts/release-notes.txt.mustache
@@ -2,43 +2,43 @@
 
 {{#changes}}
 {{#breaking}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/breaking}}
 
 {{#added}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/added}}
 
 {{#fixed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/fixed}}
 
 {{#changed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/changed}}
 
 {{#deprecated}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/deprecated}}
 
 {{#removed}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/removed}}
 
 {{#performance}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/performance}}
 
 {{#internal}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/internal}}
 
 {{#other}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/other}}
 
 {{#null}}
-* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/ligolang/ligo/-/merge_requests/{{merge_request}}))
+* {{type}}: {{{title}}} ([!{{merge_request}} by {{{author}}}](https://gitlab.com/mavryk-network/ligo/-/merge_requests/{{merge_request}}))
 {{/null}}
 
 {{/changes}}
diff --git a/src/bin/expect_tests/contract_tests.ml b/src/bin/expect_tests/contract_tests.ml
index 5cd0b87bfb..96dbde960e 100644
--- a/src/bin/expect_tests/contract_tests.ml
+++ b/src/bin/expect_tests/contract_tests.ml
@@ -253,7 +253,7 @@ let%expect_test _ =
     In a future version, `Test` will be replaced by `Test.Next`, and using `Typed_address.transfer_exn` from `Test.Next` is encouraged for a smoother migration.
 
     Everything at the top-level was executed.
-    - test exited with value 1297n. |}]
+    - test exited with value 1296n. |}]
 
 let%expect_test _ =
   run_ligo_good
diff --git a/src/bin/expect_tests/get_scope.ml b/src/bin/expect_tests/get_scope.ml
index 1d61f3b58c..b098bda1a6 100644
--- a/src/bin/expect_tests/get_scope.ml
+++ b/src/bin/expect_tests/get_scope.ml
@@ -2524,7 +2524,7 @@ let%expect_test _ =
 
 (* Unresponsive "go-to-definition" VSCode extension command
    cause by [Location.compare] behaviour w.r.t. LSet / LMap
-   (https://gitlab.com/ligolang/ligo/-/merge_requests/2532)
+   (https://gitlab.com/mavryk-network/ligo/-/merge_requests/2532)
 *)
 let%expect_test _ =
   run_ligo_good
diff --git a/src/bin/expect_tests/ligo_interpreter_tests.ml b/src/bin/expect_tests/ligo_interpreter_tests.ml
index 98afd49bcf..f1ae6e202c 100644
--- a/src/bin/expect_tests/ligo_interpreter_tests.ml
+++ b/src/bin/expect_tests/ligo_interpreter_tests.ml
@@ -852,7 +852,7 @@ let%expect_test _ =
     Warning: deprecated value.
     In a future version, `Test` will be replaced by `Test.Next`, and using `IO.log` from `Test.Next` is encouraged for a smoother migration.
 
-    Success (1279n)
+    Success (1278n)
     Everything at the top-level was executed.
     - test_timestamp exited with value (). |}]
 
@@ -4272,7 +4272,7 @@ let%expect_test _ =
     In a future version, `Test` will be replaced by `Test.Next`, and using `Typed_address.transfer` from `Test.Next` is encouraged for a smoother migration.
 
     Everything at the top-level was executed.
-    - test exited with value (1305n , 1510n , 1510n). |}]
+    - test exited with value (1304n , 1510n , 1510n). |}]
 
 let%expect_test _ =
   run_ligo_good [ "run"; "test"; test "test_implicit_account.jsligo" ];
@@ -6203,7 +6203,7 @@ let%expect_test _ =
 
     edpktom5rsehpEY6Kp2NShwsnpaaEjWxKFMJ3Rjp99VMJuHS93wxD6
     Everything at the top-level was executed.
-    - test exited with value Success (1719n). |}]
+    - test exited with value Success (1718n). |}]
 
 let%expect_test _ =
   run_ligo_good [ "run"; "test"; test "test_tickets_and_bigmaps.mligo" ];
@@ -6262,7 +6262,7 @@ let%expect_test _ =
     Warning: deprecated value.
     In a future version, `Test` will be replaced by `Test.Next`, and using `IO.log` from `Test.Next` is encouraged for a smoother migration.
 
-    Success (2672n)
+    Success (2671n)
     Everything at the top-level was executed.
     - test_one exited with value (). |}]
 
diff --git a/src/bin/repl.ml b/src/bin/repl.ml
index 089d8a297b..ea1e893cde 100644
--- a/src/bin/repl.ml
+++ b/src/bin/repl.ml
@@ -13,7 +13,7 @@ let get_declarations_core (core_prg : Ast_core.program) =
      the absolute file path, and the REPL prints an absolute file path which is confusing
      So we ignore the module declarations which which have their module_binder as some absolute path.
      The imported module name will still be printed by the REPL as it is added as a module alias.
-     Reference: https://gitlab.com/ligolang/ligo/-/blob/c8ae194e97341dc717549c9f50c743bcea855a33/vendored-dune/BuildSystem/BuildSystem.ml#L113-121
+     Reference: https://gitlab.com/mavryk-network/ligo/-/blob/c8ae194e97341dc717549c9f50c743bcea855a33/vendored-dune/BuildSystem/BuildSystem.ml#L113-121
   *)
   let ignore_module_variable_which_is_absolute_path module_variable =
     let module_variable =
diff --git a/src/main/analytics/analytics.ml b/src/main/analytics/analytics.ml
index 7e2d71322e..c769faf3c3 100644
--- a/src/main/analytics/analytics.ml
+++ b/src/main/analytics/analytics.ml
@@ -128,7 +128,7 @@ let acceptance_condition =
     ^ line_separator
     ^ " To avoid seeing this message during CI, use the --skip-analytics flag. \
        Alternatively, set the LIGO_SKIP_ANALYTICS environment variable to true. If your \
-       CI uses a Docker image, we recommend using the ligolang/ligo_ci image"
+       CI uses a Docker image, we recommend using the mavryk-network/ligo_ci image"
     ^ line_separator
     ^ " . If your change your mind, use the command `ligo analytics accept` or `ligo \
        analytics deny`."
diff --git a/src/package-management/shared/repository_url.ml b/src/package-management/shared/repository_url.ml
index 70b673d6a2..4b460e75cb 100644
--- a/src/package-management/shared/repository_url.ml
+++ b/src/package-management/shared/repository_url.ml
@@ -177,9 +177,9 @@ let%test _ =
   | _ -> false
 
 let%test _ =
-  let short = "git@github.com:ligolang/ligo-mirror.git" in
+  let short = "git@github.com:mavryk-network/ligo-mirror.git" in
   match parse_url short with
-  | Some url when String.(url = "https://github.com/ligolang/ligo-mirror.git") -> true
+  | Some url when String.(url = "https://github.com/mavryk-network/ligo-mirror.git") -> true
   | _ -> false
 
 let%test _ =
diff --git a/src/passes/04-nanopasses/passes/pattern_restriction.ml b/src/passes/04-nanopasses/passes/pattern_restriction.ml
index 34cefcd228..445d6eff9a 100644
--- a/src/passes/04-nanopasses/passes/pattern_restriction.ml
+++ b/src/passes/04-nanopasses/passes/pattern_restriction.ml
@@ -11,7 +11,7 @@ let compile ~raise =
   let pattern : _ pattern_ -> pattern = function
     | { wrap_content = P_unit; location = loc } ->
       (* For some reason we need to annotate unit pattern with unit type.
-        see https://gitlab.com/ligolang/ligo/-/issues/1700
+        see https://gitlab.com/mavryk-network/ligo/-/issues/1700
       *)
       p_typed ~loc (tv_unit ~loc ()) (p_unit ~loc)
     | { wrap_content = P_literal _; _ } as p -> raise.error (unsupported_pattern_type p)
diff --git a/src/passes/14-spilling/compiler.ml b/src/passes/14-spilling/compiler.ml
index 298228a709..3fd547a4ba 100644
--- a/src/passes/14-spilling/compiler.ml
+++ b/src/passes/14-spilling/compiler.ml
@@ -1,6 +1,6 @@
 (* The compiler is a function that takes as input the Typed AST, and outputs expressions in a language that is basically a Michelson with named variables and first-class-environments.
 
-   For more info, see back-end.md: https://gitlab.com/ligolang/ligo/blob/dev/gitlab-pages/docs/contributors/big-picture/back-end.md *)
+   For more info, see back-end.md: https://gitlab.com/mavryk-network/ligo/blob/dev/gitlab-pages/docs/contributors/big-picture/back-end.md *)
 
 module Layout_t = Layout
 open Ligo_prim
diff --git a/src/test/contracts/balance_constant.jsligo b/src/test/contracts/balance_constant.jsligo
index 0ba40adb54..b18778bfee 100644
--- a/src/test/contracts/balance_constant.jsligo
+++ b/src/test/contracts/balance_constant.jsligo
@@ -1,7 +1,7 @@
 /**
 
 This test makes sure that the balance is accessible in JsLIGO.
-It's there to detect a regression of: https://gitlab.com/ligolang/ligo/issues/61
+It's there to detect a regression of: https://gitlab.com/mavryk-network/ligo/issues/61
 
 Which results in this error when you attempt to compile this contract:
 
diff --git a/src/test/contracts/balance_constant.mligo b/src/test/contracts/balance_constant.mligo
index dcc73f4a17..eea817e066 100644
--- a/src/test/contracts/balance_constant.mligo
+++ b/src/test/contracts/balance_constant.mligo
@@ -2,7 +2,7 @@
 This test makes sure that the balance is accessible in CameLIGO.
 
 It is there to detect a regression of:
-https://gitlab.com/ligolang/ligo/issues/61
+https://gitlab.com/mavryk-network/ligo/issues/61
 
 which results in this error when you attempt to compile this contract:
 
diff --git a/src/test/contracts/let_multiple.mligo b/src/test/contracts/let_multiple.mligo
index 5d48e92b6b..06f045c782 100644
--- a/src/test/contracts/let_multiple.mligo
+++ b/src/test/contracts/let_multiple.mligo
@@ -11,13 +11,13 @@ let check_paren (_ : unit) : int = x + y
 let foobar : (int * int) = (23 , 42)
 let (foo : int) , (bar : int) = foobar
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let correct_values_bound (_ : unit) : int * int = foo, bar
 
 let non_tuple_rhs (_ : unit) : int = bar - foo
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let big_tuple : int * int * int * int * int = 10, 20, 30, 40, 50
 
@@ -26,7 +26,7 @@ let (a: int), (b: int), (c: int), (d: int), (e: int) = big_tuple
 let correct_values_big_tuple (_ : unit) : int * int * int * int * int =
   a, b, c, d, e
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let different_types : int * string = 10, "hello"
 
diff --git a/src/test/contracts/lsp/.ligo/source/i/ligo__s__bigarray__1.0.0__cf1c9d6c/Makefile b/src/test/contracts/lsp/.ligo/source/i/ligo__s__bigarray__1.0.0__cf1c9d6c/Makefile
index 56f71db631..843ec7e34b 100644
--- a/src/test/contracts/lsp/.ligo/source/i/ligo__s__bigarray__1.0.0__cf1c9d6c/Makefile
+++ b/src/test/contracts/lsp/.ligo/source/i/ligo__s__bigarray__1.0.0__cf1c9d6c/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$(PWD)":"$(PWD)" -w "$(PWD)" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$(PWD)":"$(PWD)" -w "$(PWD)" mavrykdynamics/ligo:stable
 
 .PHONY: test
 test:
diff --git a/src/test/contracts/lsp/completion_files/.ligo/source/i/ligo__s__math_lib__1.1.1__ffffffff/Makefile b/src/test/contracts/lsp/completion_files/.ligo/source/i/ligo__s__math_lib__1.1.1__ffffffff/Makefile
index 8979fccce4..8ebf91edd9 100644
--- a/src/test/contracts/lsp/completion_files/.ligo/source/i/ligo__s__math_lib__1.1.1__ffffffff/Makefile
+++ b/src/test/contracts/lsp/completion_files/.ligo/source/i/ligo__s__math_lib__1.1.1__ffffffff/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:1.0.0
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:1.0.0
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
index 471d0802ef..4c2eab42fa 100644
--- a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
+++ b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
index 3599dc4849..1e23642b67 100644
--- a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
+++ b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
index 5ceda02251..ce320eb163 100644
--- a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
+++ b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
index d842a3944c..f1b528994b 100644
--- a/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
+++ b/src/test/contracts/lsp/project_tests/project_file_in_parent/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
index 471d0802ef..4c2eab42fa 100644
--- a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
+++ b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
index 3599dc4849..1e23642b67 100644
--- a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
+++ b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/core/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
index 5ceda02251..ce320eb163 100644
--- a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
+++ b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/float/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler?=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
index d842a3944c..f1b528994b 100644
--- a/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
+++ b/src/test/contracts/lsp/project_tests/two_project_files/nested/.ligo/source/i/ligo__s__math_lib__1.1.0__ffffffff/rational/Makefile
@@ -1,4 +1,4 @@
-ligo_compiler=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" ligolang/ligo:stable
+ligo_compiler=docker run --rm -v "$$PWD":"$$PWD" -w "$$PWD" mavrykdynamics/ligo:stable
 
 PROTOCOL_OPT?=
 
diff --git a/src/test/contracts/positive/let_in_recursive.mligo b/src/test/contracts/positive/let_in_recursive.mligo
index 50b54ebd55..a3222fc626 100644
--- a/src/test/contracts/positive/let_in_recursive.mligo
+++ b/src/test/contracts/positive/let_in_recursive.mligo
@@ -1,4 +1,4 @@
-(* example from https://gitlab.com/ligolang/ligo/-/issues/1066 *)
+(* example from https://gitlab.com/mavryk-network/ligo/-/issues/1066 *)
 
 let rec ref_join
   (_params: int * (int -> int -> int))
diff --git a/src/test/error-recovery/fuzzing/cameligo/original/2let_multiple.mligo b/src/test/error-recovery/fuzzing/cameligo/original/2let_multiple.mligo
index 7b36400b98..b4cee18e41 100644
--- a/src/test/error-recovery/fuzzing/cameligo/original/2let_multiple.mligo
+++ b/src/test/error-recovery/fuzzing/cameligo/original/2let_multiple.mligo
@@ -11,13 +11,13 @@ let main_paren (_ : unit) : int = x + y
 let foobar : (int * int) = (23 , 42)
 let (foo : int) , (bar : int) = foobar
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let correct_values_bound (_ : unit) : int * int = foo, bar
 
 let non_tuple_rhs (_ : unit) : int = bar - foo
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let big_tuple : int * int * int * int * int = 10, 20, 30, 40, 50
 
@@ -26,7 +26,7 @@ let (a: int), (b: int), (c: int), (d: int), (e: int) = big_tuple
 let correct_values_big_tuple (_ : unit) : int * int * int * int * int =
   a, b, c, d, e
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let different_types : int * string = 10, "hello"
 
diff --git a/src/test/error-recovery/fuzzing/jsligo/original/4balance_constant.jsligo b/src/test/error-recovery/fuzzing/jsligo/original/4balance_constant.jsligo
index 6177b29e82..b816f4c6e5 100644
--- a/src/test/error-recovery/fuzzing/jsligo/original/4balance_constant.jsligo
+++ b/src/test/error-recovery/fuzzing/jsligo/original/4balance_constant.jsligo
@@ -1,7 +1,7 @@
 /**
 
 This test makes sure that the balance is accessible in JsLIGO.
-It's there to detect a regression of: https://gitlab.com/ligolang/ligo/issues/61
+It's there to detect a regression of: https://gitlab.com/mavryk-network/ligo/issues/61
 
 Which results in this error when you attempt to compile this contract:
 
diff --git a/src/test/transpilation/all_the_things.mligo b/src/test/transpilation/all_the_things.mligo
index 2c65eff161..8286fcb29e 100644
--- a/src/test/transpilation/all_the_things.mligo
+++ b/src/test/transpilation/all_the_things.mligo
@@ -315,7 +315,7 @@ let bar (b : int): int =
 This test makes sure that the balance is accessible in CameLIGO.
 
 It is there to detect a regression of:
-https://gitlab.com/ligolang/ligo/issues/61
+https://gitlab.com/mavryk-network/ligo/issues/61
 
 which results in this error when you attempt to compile this contract:
 
@@ -1130,13 +1130,13 @@ let main_paren (p : unit) : int = x + y
 let foobar : (int * int) = (23 , 42)
 let (foo : int) , (bar : int) = foobar
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let correct_values_bound (p : unit) : int * int = foo, bar
 
 let non_tuple_rhs (p : unit) : int = bar - foo
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let big_tuple : int * int * int * int * int = 10, 20, 30, 40, 50
 
@@ -1145,7 +1145,7 @@ let (a: int), (b: int), (c: int), (d: int), (e: int) = big_tuple
 let correct_values_big_tuple (p : unit) : int * int * int * int * int =
   a, b, c, d, e
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 
 let different_types : int * string = 10, "hello"
 
diff --git a/src/test/transpilation/expected/all_the_things.mligo.expected b/src/test/transpilation/expected/all_the_things.mligo.expected
index 7332cd074c..3f5f1758cd 100644
--- a/src/test/transpilation/expected/all_the_things.mligo.expected
+++ b/src/test/transpilation/expected/all_the_things.mligo.expected
@@ -478,7 +478,7 @@ let bar (b : int) : int =
 This test makes sure that the balance is accessible in CameLIGO.
 
 It is there to detect a regression of:
-https://gitlab.com/ligolang/ligo/issues/61
+https://gitlab.com/mavryk-network/ligo/issues/61
 
 which results in this error when you attempt to compile this contract:
 
@@ -1480,12 +1480,12 @@ let foobar : (int * int) = (23, 42)
 
 let (foo : int), (bar : int) = foobar
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 let correct_values_bound (p : unit) : int * int = foo, bar
 
 let non_tuple_rhs (p : unit) : int = bar - foo
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 let big_tuple : int * int * int * int * int =
   10, 20, 30, 40, 50
 
@@ -1495,7 +1495,7 @@ let (a : int), (b : int), (c : int), (d : int), (e : int) =
 let correct_values_big_tuple (p : unit)
 : int * int * int * int * int = a, b, c, d, e
 
-(* Here to prevent a regression of https://gitlab.com/ligolang/ligo/issues/63#note_254106580 *)
+(* Here to prevent a regression of https://gitlab.com/mavryk-network/ligo/issues/63#note_254106580 *)
 let different_types : int * string = 10, "hello"
 
 let (greet_num : int), (greeting : string) = different_types
diff --git a/tools/debugger/docs/ligo-versions.md b/tools/debugger/docs/ligo-versions.md
index 866686ed3b..9ab45b1ef0 100644
--- a/tools/debugger/docs/ligo-versions.md
+++ b/tools/debugger/docs/ligo-versions.md
@@ -30,7 +30,7 @@ When anybody notices that a new version of `ligo` is released, he is free to cre
 This commit can be created in a new MR or in any existing MR just by the way, as upper version bump should happen often and we want to have this process simple.
 Running tests is a sufficient proof of that the new version can be treated as supported.
 
-Also, we should periodically check when a new verion of `ligo` is released, e.g. at [this page](https://gitlab.com/ligolang/ligo/-/releases).
+Also, we should periodically check when a new verion of `ligo` is released, e.g. at [this page](https://gitlab.com/mavryk-network/ligo/-/releases).
 
 ### Lower bound
 
diff --git a/tools/debugger/ligo-debugger/src/Language/LIGO/Debugger/CLI/Types.hs b/tools/debugger/ligo-debugger/src/Language/LIGO/Debugger/CLI/Types.hs
index 8479730f53..32c36400b4 100644
--- a/tools/debugger/ligo-debugger/src/Language/LIGO/Debugger/CLI/Types.hs
+++ b/tools/debugger/ligo-debugger/src/Language/LIGO/Debugger/CLI/Types.hs
@@ -982,7 +982,7 @@ fromLigoType
   -> LIGO Info
 fromLigoType st = \case
   LTCConstant LigoTypeConstant {..} ->
-    -- See: https://gitlab.com/ligolang/ligo/-/issues/1478
+    -- See: https://gitlab.com/mavryk-network/ligo/-/issues/1478
     fromLigoConstant (_ltcInjection & over _head toLower) _ltcParameters
 
   LTCVariable variable -> fromLigoVariable variable
diff --git a/tools/debugger/ligo-debugger/test/Test/LigoCall.hs b/tools/debugger/ligo-debugger/test/Test/LigoCall.hs
index 339a6f9f28..bd25df6bc2 100644
--- a/tools/debugger/ligo-debugger/test/Test/LigoCall.hs
+++ b/tools/debugger/ligo-debugger/test/Test/LigoCall.hs
@@ -87,7 +87,7 @@ test_ExpressionCompilation = testGroup "Compiling expression"
 
   , testGroup "Expressions starting from `-`"
     -- At the moment of writing, `ligo` does not accept negative numbers easily
-    -- See https://gitlab.com/ligolang/ligo/-/issues/1495
+    -- See https://gitlab.com/mavryk-network/ligo/-/issues/1495
     [ testCase "Negative numbers" do
         res <- evalExprOverContract1 "-3"
         res @?= U.ValueInt (-3)
diff --git a/tools/emacs/ligo-mode.el b/tools/emacs/ligo-mode.el
index 92a84a77f7..de7c370f7a 100644
--- a/tools/emacs/ligo-mode.el
+++ b/tools/emacs/ligo-mode.el
@@ -3,7 +3,7 @@
 
 ;; Version: 0.2.0
 ;; Author: LigoLang SASU
-;; Url: https://gitlab.com/ligolang/ligo/-/tree/dev/tools/emacs
+;; Url: https://gitlab.com/mavryk-network/ligo/-/tree/dev/tools/emacs
 ;; Keywords: languages
 ;; Package-Requires: ((emacs "27.1"))
 
diff --git a/tools/ligo-snippets/README.md b/tools/ligo-snippets/README.md
index 58c9690e62..1736f6fcbd 100644
--- a/tools/ligo-snippets/README.md
+++ b/tools/ligo-snippets/README.md
@@ -2,12 +2,12 @@ A React component for embedding Ligo code snippets on a page.
 
 # Quick start
 
-1. Install package `yarn add @ligolang/ligo-snippets`
+1. Install package `yarn add @mavryk-network/ligo-snippets`
 2. Add `LigoSnippet` component to a page
 
 
 ```jsx
-import { LigoSnippet } from "@ligolang/ligo-snippets";
+import { LigoSnippet } from "@mavryk-network/ligo-snippets";
 
 const App = () => {
     const code = `type storage is int
diff --git a/tools/ligo-snippets/package-lock.json b/tools/ligo-snippets/package-lock.json
index 20fc06994e..2d5ce2ff55 100644
--- a/tools/ligo-snippets/package-lock.json
+++ b/tools/ligo-snippets/package-lock.json
@@ -1,5 +1,5 @@
 {
-  "name": "@ligolang/ligo-snippets",
+  "name": "@mavryk-network/ligo-snippets",
   "version": "1.0.1",
   "lockfileVersion": 1,
   "requires": true,
diff --git a/tools/ligo-snippets/package.json b/tools/ligo-snippets/package.json
index d0bc6151a5..ac6cc9a2d3 100644
--- a/tools/ligo-snippets/package.json
+++ b/tools/ligo-snippets/package.json
@@ -1,5 +1,5 @@
 {
-  "name": "@ligolang/ligo-snippets",
+  "name": "@mavryk-network/ligo-snippets",
   "version": "1.0.1",
   "main": "./lib/index.js",
   "scripts": {
diff --git a/tools/vscode/README.md b/tools/vscode/README.md
index 6529c33397..1ad9f16867 100644
--- a/tools/vscode/README.md
+++ b/tools/vscode/README.md
@@ -10,7 +10,7 @@ Language Server capabilities on Windows are supported only if running in WSL mod
 Note: You need a LIGO build with support for `ligo lsp`.
 LIGO version 0.61.0 and greater come with support for language server capabilities.
 
-To report bugs in the LIGO Language Server (LLS), please open an issue in [GitLab](https://gitlab.com/ligolang/ligo/-/issues).
+To report bugs in the LIGO Language Server (LLS), please open an issue in [GitLab](https://gitlab.com/mavryk-network/ligo/-/issues).
 You should find a file called `ligo_language_server.log` in your temporary directory. For example, in Linux, this should be inside `/tmp/`, which might contain information that the devs would find useful to debug your problem.
 
 Version 0.5.0 brings a rewrite of the language server in OCaml to improve the perfomance, stability, and more functionalities implemented in the LIGO compiler.
@@ -154,7 +154,7 @@ Also, if you prefer using `ligo` from the Docker image then you can specify a pa
 
 ```sh
 #!/bin/sh
-docker run --rm -v $(pwd):$(pwd) -w $(pwd) ligolang/ligo:{ligo-version} "$@"
+docker run --rm -v $(pwd):$(pwd) -w $(pwd) mavrykdynamics/ligo:{ligo-version} "$@"
 ```
 
 where `{ligo-version}` is your preferred `ligo` version (e.g. `0.70.1`).
diff --git a/tools/vscode/client/src/common/LigoProtocolClient.ts b/tools/vscode/client/src/common/LigoProtocolClient.ts
index c102446471..f0b3b31211 100644
--- a/tools/vscode/client/src/common/LigoProtocolClient.ts
+++ b/tools/vscode/client/src/common/LigoProtocolClient.ts
@@ -145,7 +145,7 @@ export function processErrorResponse(response: DebugProtocol.ErrorResponse): voi
               latestSupported = "";
             }
 
-            vscode.env.openExternal(vscode.Uri.parse("https://gitlab.com/ligolang/ligo/-/releases/" + latestSupported))
+            vscode.env.openExternal(vscode.Uri.parse("https://gitlab.com/mavryk-network/ligo/-/releases/" + latestSupported))
               .then(result => {
                 if (!result) {
                   vscode.window.showErrorMessage("Failed to open LIGO releases page.");
diff --git a/tools/vscode/client/src/lsp/updateLigo.ts b/tools/vscode/client/src/lsp/updateLigo.ts
index 60e8256d5b..6c5c6c5b9c 100644
--- a/tools/vscode/client/src/lsp/updateLigo.ts
+++ b/tools/vscode/client/src/lsp/updateLigo.ts
@@ -155,7 +155,7 @@ async function getLatestLigoRelease(): Promise<Release> {
 }
 
 function openLigoReleases(): Thenable<boolean> {
-  return vscode.env.openExternal(vscode.Uri.parse('https://gitlab.com/ligolang/ligo/-/releases'))
+  return vscode.env.openExternal(vscode.Uri.parse('https://gitlab.com/mavryk-network/ligo/-/releases'))
     .then((result) => {
       if (!result) {
         vscode.window.showErrorMessage('Failed to open LIGO releases page.')
@@ -175,15 +175,15 @@ const ligoTempDownloadTemplate: string = path.join(os.tmpdir(), 'ligo-bin-')
 
 async function runBrewInstaller(client: LanguageClient): Promise<null> {
   const terminal = mkTerminal()
-  terminal.sendText(`brew tap ligolang/ligo https://gitlab.com/ligolang/ligo.git`)
-  await withClientRestart(client, () => terminal.sendText(`brew install ligolang/ligo/ligo`))
+  terminal.sendText(`brew tap mavryk-network/ligo https://gitlab.com/mavryk-network/ligo.git`)
+  await withClientRestart(client, () => terminal.sendText(`brew install mavryk-network/ligo/ligo`))
   return null
 }
 
 async function runBrewUpgrade(client: LanguageClient): Promise<null> {
   const terminal = mkTerminal()
   terminal.sendText(`brew update`)
-  await withClientRestart(client, () => terminal.sendText(`brew upgrade ligolang/ligo/ligo`))
+  await withClientRestart(client, () => terminal.sendText(`brew upgrade mavryk-network/ligo/ligo`))
   return null
 }
 
diff --git a/tools/vscode/package.json b/tools/vscode/package.json
index 97d70d48a4..26124c8d02 100644
--- a/tools/vscode/package.json
+++ b/tools/vscode/package.json
@@ -7,7 +7,7 @@
     "version": "1.4.0",
     "repository": {
         "type": "git",
-        "url": "https://gitlab.com/ligolang/ligo"
+        "url": "https://gitlab.com/mavryk-network/ligo"
     },
     "publisher": "ligolang-publish",
     "categories": [
@@ -87,7 +87,7 @@
                     "scope": "resource",
                     "type": "array",
                     "default": [],
-                    "markdownDescription": "Disable specific LIGO LSP features. For a list of features, see [the README.md](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vscode/README.md)."
+                    "markdownDescription": "Disable specific LIGO LSP features. For a list of features, see [the README.md](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vscode/README.md)."
                 },
                 "ligoLanguageServer.tezos_source_account": {
                     "scope": "resource",
@@ -114,7 +114,7 @@
                         "null"
                     ],
                     "default": null,
-                    "markdownDescription": "Sets custom max line width for a formatted file. Default is 80. If a custom `printWidth` is set in `.ligopretty` file, this setting has no effect (see [the README.md](https://gitlab.com/ligolang/ligo/-/blob/dev/tools/vscode/README.md)). Requires LIGO 0.67.0 or newer."
+                    "markdownDescription": "Sets custom max line width for a formatted file. Default is 80. If a custom `printWidth` is set in `.ligopretty` file, this setting has no effect (see [the README.md](https://gitlab.com/mavryk-network/ligo/-/blob/dev/tools/vscode/README.md)). Requires LIGO 0.67.0 or newer."
                 },
                 "ligoLanguageServer.completionImplementation": {
                     "scope": "resource",
diff --git a/tools/webide-new/flake.nix b/tools/webide-new/flake.nix
index c3f67f9d24..8192582ab6 100644
--- a/tools/webide-new/flake.nix
+++ b/tools/webide-new/flake.nix
@@ -109,7 +109,7 @@
         localSystem = system;
       };
       ligo-binary = {
-        "x86_64-linux" = { url = "https://gitlab.com/ligolang/ligo/-/jobs/4687472710/artifacts/raw/ligo"; hash = "sha256-wwxc2Sncq1ojcdVLv1FbFxc4FHbz2t9Fw3oJPCKMVSI="; };
+        "x86_64-linux" = { url = "https://gitlab.com/mavryk-network/ligo/-/jobs/4687472710/artifacts/raw/ligo"; hash = "sha256-wwxc2Sncq1ojcdVLv1FbFxc4FHbz2t9Fw3oJPCKMVSI="; };
       };
       ligo-syntaxes = pkgs.callPackage ../vscode/syntaxes {};
       tezos-client = inputs.tezos-packaging.packages.${system}.tezos-client;
diff --git a/tools/webide-new/ligo-webide-backend/Dockerfile b/tools/webide-new/ligo-webide-backend/Dockerfile
index 8419c2c6fe..992ba73ba8 100644
--- a/tools/webide-new/ligo-webide-backend/Dockerfile
+++ b/tools/webide-new/ligo-webide-backend/Dockerfile
@@ -1,5 +1,5 @@
 FROM tezos/tezos:latest as octez-client
-FROM ligolang/ligo:1.4.0 as ligo-compiler
+FROM mavrykdynamics/ligo:1.4.0 as ligo-compiler
 FROM ubuntu:20.04 as web-ide-builder
 
 LABEL maintainer="infra@marigold.dev"
diff --git a/tools/webide-new/ligo-webide-backend/src/Ligo.hs b/tools/webide-new/ligo-webide-backend/src/Ligo.hs
index 141766cc3b..d6bb14ed0b 100644
--- a/tools/webide-new/ligo-webide-backend/src/Ligo.hs
+++ b/tools/webide-new/ligo-webide-backend/src/Ligo.hs
@@ -24,7 +24,7 @@ runLigo dirPath commands = do
         , dirPath ++ ":" ++ dirPath
         , "-w"
         , dirPath
-        , "ligolang/ligo_ci:" ++ version
+        , "mavryk-network/ligo_ci:" ++ version
         ]
         ++ commands
     Nothing -> do
diff --git a/tools/webide-new/ligo-webide-frontend/README.md b/tools/webide-new/ligo-webide-frontend/README.md
index a11748a5ea..c7ed973b1c 100644
--- a/tools/webide-new/ligo-webide-frontend/README.md
+++ b/tools/webide-new/ligo-webide-frontend/README.md
@@ -6,7 +6,7 @@ On `ligo-ide` run `yarn install` to install dependencies, `yarn build:react` to
 Also for working with `git` you need to specify `GIT_PROXY` env variable. This proxy is required by one of the dependencies, see https://github.com/isomorphic-git/isomorphic-git#cors-support. For connecting to the backend, you need to specify a `BACKEND_URL` env variable and `HTTP_PROTOCOL` which can be `http`or `https`.
 
 To build with Docker, provide backend url with the arg `--build-arg backend_url`.
-To generate a release, push a new branch named `webide-release/frontend` on https://gitlab.com/ligolang/ligo. The CI will generate a new image and push it into [gitlab container registry](https://gitlab.com/ligolang/ligo/container_registry/3546999)
+To generate a release, push a new branch named `webide-release/frontend` on https://gitlab.com/mavryk-network/ligo. The CI will generate a new image and push it into [gitlab container registry](https://gitlab.com/mavryk-network/ligo/container_registry/3546999)
 
 ## Deploy
 
diff --git a/vendored-dune/GetoptLib/GetoptLib.opam b/vendored-dune/GetoptLib/GetoptLib.opam
index ec1e795ffd..6fd720cdc6 100644
--- a/vendored-dune/GetoptLib/GetoptLib.opam
+++ b/vendored-dune/GetoptLib/GetoptLib.opam
@@ -8,7 +8,7 @@ features of GNU getopt and getopt_long. The module Getopt is an alternative; it
 maintainer   : "Christian Rinderknecht <rinderknecht@free.fr>"
 authors      : "Alain Frisch"
 homepage     : "https://github.com/gildor478/ocaml-getopt"
-bug-reports  : "https://gitlab.com/ligolang/ligo/-/issues"
+bug-reports  : "https://gitlab.com/mavryk-network/ligo/-/issues"
 license      : "MIT"
 
 # If you change the dependencies, run `opam lock` in the root
diff --git a/vendored-dune/ligo-utils/proto-alpha-utils/proto-alpha-utils.opam b/vendored-dune/ligo-utils/proto-alpha-utils/proto-alpha-utils.opam
index 6eec5b1a8b..c6fe0b4915 100644
--- a/vendored-dune/ligo-utils/proto-alpha-utils/proto-alpha-utils.opam
+++ b/vendored-dune/ligo-utils/proto-alpha-utils/proto-alpha-utils.opam
@@ -7,8 +7,8 @@ synopsis: "LIGO Proto Alpha-specific Utilities, to be used by other libraries"
 maintainer: "Galfour <contact@ligolang.org>"
 authors: "Galfour <contact@ligolang.org>"
 license: "MIT"
-homepage: "https://gitlab.com/ligolang/ligo-utils"
-bug-reports: "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage: "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports: "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends: [
   "dune"
diff --git a/vendored-dune/ligo-utils/proto-pre-alpha-utils/proto-pre-alpha-utils.opam b/vendored-dune/ligo-utils/proto-pre-alpha-utils/proto-pre-alpha-utils.opam
index 3bdd250415..ed60d664ac 100644
--- a/vendored-dune/ligo-utils/proto-pre-alpha-utils/proto-pre-alpha-utils.opam
+++ b/vendored-dune/ligo-utils/proto-pre-alpha-utils/proto-pre-alpha-utils.opam
@@ -7,8 +7,8 @@ synopsis: "LIGO Proto Pre-Alpha-specific Utilities, to be used by other librarie
 maintainer: "Galfour <contact@ligolang.org>"
 authors: "Galfour <contact@ligolang.org>"
 license: "MIT"
-homepage: "https://gitlab.com/ligolang/ligo-utils"
-bug-reports: "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage: "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports: "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends: [
   "dune"
diff --git a/vendored-dune/ligo-utils/simple-utils/simple-utils-js.opam b/vendored-dune/ligo-utils/simple-utils/simple-utils-js.opam
index 96a5008c09..09c1650f34 100644
--- a/vendored-dune/ligo-utils/simple-utils/simple-utils-js.opam
+++ b/vendored-dune/ligo-utils/simple-utils/simple-utils-js.opam
@@ -7,8 +7,8 @@ synopsis     : "LIGO utilities with Unix APIs linked in"
 maintainer   : "Galfour <contact@ligolang.org>"
 authors      : "Galfour, Christian Rinderknecht"
 license      : "MIT"
-homepage     : "https://gitlab.com/ligolang/ligo-utils"
-bug-reports  : "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage     : "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports  : "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends      : ["dune"
                 "base"
diff --git a/vendored-dune/ligo-utils/simple-utils/simple-utils-unix.opam b/vendored-dune/ligo-utils/simple-utils/simple-utils-unix.opam
index 96a5008c09..09c1650f34 100644
--- a/vendored-dune/ligo-utils/simple-utils/simple-utils-unix.opam
+++ b/vendored-dune/ligo-utils/simple-utils/simple-utils-unix.opam
@@ -7,8 +7,8 @@ synopsis     : "LIGO utilities with Unix APIs linked in"
 maintainer   : "Galfour <contact@ligolang.org>"
 authors      : "Galfour, Christian Rinderknecht"
 license      : "MIT"
-homepage     : "https://gitlab.com/ligolang/ligo-utils"
-bug-reports  : "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage     : "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports  : "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends      : ["dune"
                 "base"
diff --git a/vendored-dune/ligo-utils/simple-utils/simple-utils.opam b/vendored-dune/ligo-utils/simple-utils/simple-utils.opam
index 0c8e94df52..76291fc4da 100644
--- a/vendored-dune/ligo-utils/simple-utils/simple-utils.opam
+++ b/vendored-dune/ligo-utils/simple-utils/simple-utils.opam
@@ -7,8 +7,8 @@ synopsis     : "LIGO utilities"
 maintainer   : "Galfour <contact@ligolang.org>"
 authors      : "Galfour, Christian Rinderknecht"
 license      : "MIT"
-homepage     : "https://gitlab.com/ligolang/ligo-utils"
-bug-reports  : "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage     : "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports  : "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends      : ["dune"
                 "base"
diff --git a/vendored-dune/ligo-utils/tezos-utils/tezos-utils.opam b/vendored-dune/ligo-utils/tezos-utils/tezos-utils.opam
index 958f70663d..8e613c6e33 100644
--- a/vendored-dune/ligo-utils/tezos-utils/tezos-utils.opam
+++ b/vendored-dune/ligo-utils/tezos-utils/tezos-utils.opam
@@ -7,8 +7,8 @@ synopsis: "LIGO Tezos specific Utilities, to be used by other libraries"
 maintainer: "Galfour <contact@ligolang.org>"
 authors: "Galfour <contact@ligolang.org>"
 license: "MIT"
-homepage: "https://gitlab.com/ligolang/ligo-utils"
-bug-reports: "https://gitlab.com/ligolang/ligo-utils/issues"
+homepage: "https://gitlab.com/mavryk-network/ligo-utils"
+bug-reports: "https://gitlab.com/mavryk-network/ligo-utils/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends: [
   "dune"
diff --git a/vendored-dune/syntax-highlighting/Emacs.ml b/vendored-dune/syntax-highlighting/Emacs.ml
index d1f164f0e3..ec1ac70686 100644
--- a/vendored-dune/syntax-highlighting/Emacs.ml
+++ b/vendored-dune/syntax-highlighting/Emacs.ml
@@ -340,7 +340,7 @@ For debugging.
     fprintf fmt ";;; ligo-mode.el --- A major mode for editing LIGO source code\n\n";
     fprintf fmt ";; Version: 0.2.0\n";
     fprintf fmt ";; Author: LigoLang SASU\n";
-    fprintf fmt ";; Url: https://gitlab.com/ligolang/ligo/-/tree/dev/tools/emacs\n";
+    fprintf fmt ";; Url: https://gitlab.com/mavryk-network/ligo/-/tree/dev/tools/emacs\n";
     fprintf fmt ";; Keywords: languages\n";
     fprintf fmt ";; Package-Requires: ((emacs \"27.1\"))\n\n";
     fprintf fmt ";; This file is distributed under the terms of the MIT license.\n\n";
diff --git a/vendored-dune/syntax-highlighting/SyntaxHighlighting.opam b/vendored-dune/syntax-highlighting/SyntaxHighlighting.opam
index 4e0e94a042..3a498a8b0a 100644
--- a/vendored-dune/syntax-highlighting/SyntaxHighlighting.opam
+++ b/vendored-dune/syntax-highlighting/SyntaxHighlighting.opam
@@ -6,8 +6,8 @@ description  : "Generate syntax highlighting for TextMate, Vim, and Emacs."
 maintainer   : "info@ligolang.org"
 authors      : "LIGO team"
 license      : "MIT"
-homepage     : "https://gitlab.com/ligolang/ligo/-/tree/dev/vendored-dune/syntax-highlighting"
-bug-reports  : "https://gitlab.com/ligolang/ligo/issues"
+homepage     : "https://gitlab.com/mavryk-network/ligo/-/tree/dev/vendored-dune/syntax-highlighting"
+bug-reports  : "https://gitlab.com/mavryk-network/ligo/issues"
 # If you change the dependencies, run `opam lock` in the root
 depends      : ["dune" "yojson"]
 build        : [