update packages

.github/ISSUE_TEMPLATE.md

@@ -1,3 +1,3 @@
-## 👉 [Please follow one of these issue templates](https://github.com/AleoHQ/leo/issues/new/choose) 👈
+## 👉 [Please follow one of these issue templates](https://github.com/ProvableHQ/leo/issues/new/choose) 👈
 
 Note: to keep the backlog clean and actionable, issues may be immediately closed if they do not follow one of the above issue templates.

.github/PULL_REQUEST_TEMPLATE.md

@@ -24,7 +24,7 @@
 
 <!--
     If this PR adds or changes functionality,
-    please take some time to update the docs at https://github.com/AleoHQ/leo,
+    please take some time to update the docs at https://github.com/ProvableHQ/leo,
     and link to your PR here.
 -->
 

.resources/license_header

@@ -1,4 +1,4 @@
-// Copyright (C) 2019-2023 Aleo Systems Inc.
+// Copyright (C) 2019-2024 Aleo Systems Inc.
 // This file is part of the Leo library.
 
 // The Leo library is free software: you can redistribute it and/or modify
@@ -12,4 +12,4 @@
 // GNU General Public License for more details.
 
 // You should have received a copy of the GNU General Public License
-// along with the Leo library. If not, see <https://www.gnu.org/licenses/>.
+// along with the Leo library. If not, see <https://www.gnu.org/licenses/>.

.resources/release-version

@@ -1 +1 @@
-v2.1.0
+v2.3.0

.rustfmt.toml

@@ -13,4 +13,4 @@ imports_layout = "HorizontalVertical"
 imports_granularity = "Crate"
 overflow_delimited_expr = true
 reorder_impl_items = true
-version = "Two"
+style_edition = "2024"

CONTRIBUTING.md

@@ -6,7 +6,7 @@ Thank you for your interest in contributing to Leo! Below you can find some guid
 
 Please follow the instructions below when filing pull requests:
 
-- Ensure that your branch is forked from the current [mainnet](https://github.com/AleoHQ/leo/tree/mainnet) branch.
+- Ensure that your branch is forked from the current [mainnet](https://github.com/ProvableHQ/leo/tree/mainnet) branch.
 - Fill out the provided markdown template for the feature or proposal. Be sure to link the pull request to any issues by using keywords. Example: "closes #130".
 - Run `cargo fmt` before you commit; we use the `nightly` version of `rustfmt` to format the code, so you'll need to have the `nightly` toolchain installed on your machine; there's a [git hook](https://git-scm.com/docs/githooks) that ensures proper formatting before any commits can be made, and [`.rustfmt.toml`](https://github.com/AleoHQ/Leo/blob/mainnet/.rustfmt.toml) specifies some of the formatting conventions.
 - Run `cargo clippy` to ensure that popular correctness and performance pitfalls are avoided.