From 8f754e30eb66d8f4fb065fe838191e59c36f0695 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Tue, 25 Aug 2026 17:49:46 +0200 Subject: [PATCH 01/15] Document release steps --- README.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/README.md b/README.md index 6a40eea..a44db6b 100644 --- a/README.md +++ b/README.md @@ -118,6 +118,32 @@ just deploy J516Mv7YvvvJyMvNEca8tWNTJyDHbFpzwDZD96BNfR3w ~/solana-keys/deployer. The deployer for the canonical devnet program (`J516Mv7YvvvJyMvNEca8tWNTJyDHbFpzwDZD96BNfR3w`) is stored in the team password manager under `B6acm3swJK9pJ7fe4i4GQgP7x5A3RndvsdV2bKhcA1i5`. +## Alpha releases + +There are two possible release flows while the project is in alpha: +- Program breaking change: the logic of the program changes meaningfully or there's some change on the layout of _any_ PDA. +- Patch update: it's mostly a hotfix for the program that doesn't meaningfully change the program state. The old client/interface should still work with the new program code. + +You can use the settle CLI for a smoke test of the programs after a release. See `cargo run -p cow-test-cli -- sell --help` and `cargo run -p cow-test-cli -- settle --help`. + +### Breaking change + +- Bump the version in all `./**/Cargo.toml` files *by at least a minor version*. For example, `VERSION=0.42.1337`. +- Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. +- Store the newly generated account [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com). +- Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. +- Commit the changes. +- [Deploy the programs](#how-to-deploy). The deployer keypair is [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com). The program keypair file is the key that was generated before. +- Initialize the new deployment. See `cargo run -p cow-test-cli -- initialize --help`. +- [Publish the cargo packages](#publishing-the-cargo-packages). + +### Patch update + +- Bump the version in all `./**/Cargo.toml` files by a patch version. +- Commit the changes. +- [Update the programs](#how-to-deploy). The [deployer keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com) and the [program keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com) are in 1password. +- [Publish the cargo packages](#publishing-the-cargo-packages). + ## License [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](./COPYING.MIT) [![License: Apache v2.0](https://img.shields.io/badge/License-Apache_2.0-green.svg)](./COPYING.APACHE) [![License: LGPL v3](https://img.shields.io/badge/License-LGPLv3-blue.svg)](./COPYING.LESSER) From 94863509008136f0df36640eac033b6a1efa6347 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Tue, 25 Aug 2026 18:00:42 +0200 Subject: [PATCH 02/15] Add PR step --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index a44db6b..0030e6f 100644 --- a/README.md +++ b/README.md @@ -135,12 +135,14 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Commit the changes. - [Deploy the programs](#how-to-deploy). The deployer keypair is [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com). The program keypair file is the key that was generated before. - Initialize the new deployment. See `cargo run -p cow-test-cli -- initialize --help`. +- Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). ### Patch update - Bump the version in all `./**/Cargo.toml` files by a patch version. - Commit the changes. +- Create a PR with the changes and wait for approval. - [Update the programs](#how-to-deploy). The [deployer keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com) and the [program keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com) are in 1password. - [Publish the cargo packages](#publishing-the-cargo-packages). From 8b59def318a67daab88b722076d1e863c52dc753 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Wed, 26 Aug 2026 14:51:25 +0200 Subject: [PATCH 03/15] Clarify version bump --- README.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0030e6f..9ba9d4a 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See ### Breaking change -- Bump the version in all `./**/Cargo.toml` files *by at least a minor version*. For example, `VERSION=0.42.1337`. +- [Bump the crate version](#bumping-the-crate-version) *by at least a minor version*. - Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. - Store the newly generated account [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com). - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. @@ -140,12 +140,26 @@ You can use the settle CLI for a smoke test of the programs after a release. See ### Patch update -- Bump the version in all `./**/Cargo.toml` files by a patch version. +- [Bump the crate version](#bumping-the-crate-version) by a patch version. - Commit the changes. - Create a PR with the changes and wait for approval. - [Update the programs](#how-to-deploy). The [deployer keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com) and the [program keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com) are in 1password. - [Publish the cargo packages](#publishing-the-cargo-packages). +### Bumping the crate version + +You need to update Cargo's toml and lock file. +Here is a list of commands to help bumping all relevant strings: + +```sh +export VERSION=0.42.1337 +perl -i -pe ' + s/^version = ".*"/version = "$ENV{VERSION}"/; + s/(path = "[^"]*", version = )"[^"]*"/$1"$ENV{VERSION}"/; +' ./Cargo.toml +just build +``` + ## License [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](./COPYING.MIT) [![License: Apache v2.0](https://img.shields.io/badge/License-Apache_2.0-green.svg)](./COPYING.APACHE) [![License: LGPL v3](https://img.shields.io/badge/License-LGPLv3-blue.svg)](./COPYING.LESSER) From 6644acc7180e4005efbc5198af6e1dc1db2a001e Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Wed, 26 Aug 2026 14:55:45 +0200 Subject: [PATCH 04/15] Remove direct links to 1password --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9ba9d4a..d6ecaf6 100644 --- a/README.md +++ b/README.md @@ -130,10 +130,10 @@ You can use the settle CLI for a smoke test of the programs after a release. See - [Bump the crate version](#bumping-the-crate-version) *by at least a minor version*. - Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. -- Store the newly generated account [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com). +- Store the newly generated account in 1password (under "Settlement account by version"). - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. - Commit the changes. -- [Deploy the programs](#how-to-deploy). The deployer keypair is [in 1password](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com). The program keypair file is the key that was generated before. +- [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. - Initialize the new deployment. See `cargo run -p cow-test-cli -- initialize --help`. - Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). @@ -143,7 +143,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - [Bump the crate version](#bumping-the-crate-version) by a patch version. - Commit the changes. - Create a PR with the changes and wait for approval. -- [Update the programs](#how-to-deploy). The [deployer keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ch65n5b6akn4peqbrvsmelorlq&h=cowserviceslda.1password.com) and the [program keypair](https://start.1password.com/open/i?a=6DWD777JFFEZZLYS6J4DUURYLE&v=j72yup55epeqinjrndwns5yuse&i=ie6sd53uo6rawl43sd4373zq5i&h=cowserviceslda.1password.com) are in 1password. +- [Update the programs](#how-to-deploy). The deployer keypair and the program keypair are in 1password (stored respectively under "Solana Deployer" and "Settlement account by version"). - [Publish the cargo packages](#publishing-the-cargo-packages). ### Bumping the crate version From 47986c412f875ede3e01da334fe9481d87e32f23 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Wed, 26 Aug 2026 14:58:22 +0200 Subject: [PATCH 05/15] More explicit commit instructions --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d6ecaf6..bb6aaaa 100644 --- a/README.md +++ b/README.md @@ -132,16 +132,16 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. - Store the newly generated account in 1password (under "Settlement account by version"). - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. -- Commit the changes. +- Commit the code changes resulting from the changes above (not the account). - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. - Initialize the new deployment. See `cargo run -p cow-test-cli -- initialize --help`. -- Create a PR with the changes and wait for approval. +- Create a PR with the changes (branch `release/v*.*.*`) and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). ### Patch update - [Bump the crate version](#bumping-the-crate-version) by a patch version. -- Commit the changes. +- Commit the code changes resulting from the changes above. - Create a PR with the changes and wait for approval. - [Update the programs](#how-to-deploy). The deployer keypair and the program keypair are in 1password (stored respectively under "Solana Deployer" and "Settlement account by version"). - [Publish the cargo packages](#publishing-the-cargo-packages). From f88dcc684be76e5455d860e7d20e44d83f714c39 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Wed, 26 Aug 2026 14:59:18 +0200 Subject: [PATCH 06/15] Remove unnecessary initialization --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index bb6aaaa..fe5a9e9 100644 --- a/README.md +++ b/README.md @@ -134,7 +134,6 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. - Commit the code changes resulting from the changes above (not the account). - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. -- Initialize the new deployment. See `cargo run -p cow-test-cli -- initialize --help`. - Create a PR with the changes (branch `release/v*.*.*`) and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). From a3eb22c35ea2e854d7ce08a90554c78feb57c448 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 10:34:08 +0200 Subject: [PATCH 07/15] Clarify generated account --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fe5a9e9..fda3cac 100644 --- a/README.md +++ b/README.md @@ -132,9 +132,9 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. - Store the newly generated account in 1password (under "Settlement account by version"). - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. -- Commit the code changes resulting from the changes above (not the account). +- Commit the code changes resulting from the steps above (excluding the key of the generated account). - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. -- Create a PR with the changes (branch `release/v*.*.*`) and wait for approval. +- Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). ### Patch update From 7c30a30f55ad62c3657a7d86b2bdf10f230fb8ae Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 17:42:17 +0200 Subject: [PATCH 08/15] Specify that releases are based on main --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index fda3cac..fa2b486 100644 --- a/README.md +++ b/README.md @@ -128,6 +128,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See ### Breaking change +- Check out the `main` branch. Make sure there are no local changes (`git status --porcelain` is empty). - [Bump the crate version](#bumping-the-crate-version) *by at least a minor version*. - Generate a new account (`solana-keygen new --no-bip39-passphrase -o ../deploy-v$VERSION.json`). This will be the address of the new deployment. - Store the newly generated account in 1password (under "Settlement account by version"). @@ -139,6 +140,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See ### Patch update +- Check out the `main` branch. Make sure there are no local changes (`git status --porcelain` is empty). - [Bump the crate version](#bumping-the-crate-version) by a patch version. - Commit the code changes resulting from the changes above. - Create a PR with the changes and wait for approval. From 04475e36a2664b38ee8b3f687ac67491d2ecba99 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 17:49:51 +0200 Subject: [PATCH 09/15] Add step to authorize solvers --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index fa2b486..902c916 100644 --- a/README.md +++ b/README.md @@ -135,6 +135,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. - Commit the code changes resulting from the steps above (excluding the key of the generated account). - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. +- Authorize all [currently existing solver](https://app.notion.com/p/cownation/Solvers-for-Solana-Dev-Contracts-3ca8da5f04ca80968642e85640178cbd) using the solver CLI (`cow solver add --help`). - Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). From 29fa83b3aac51bbccb849f83a95d26c4017d8439 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:02:25 +0200 Subject: [PATCH 10/15] Specify network --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 902c916..c956abd 100644 --- a/README.md +++ b/README.md @@ -134,6 +134,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Store the newly generated account in 1password (under "Settlement account by version"). - Update the account in `solana_pubkey::declare_id!` to the new account. Search and replace entries with the old account to the newly generated address. - Commit the code changes resulting from the steps above (excluding the key of the generated account). +- Switch your network to mainnet (`solana config set --url mainnet-beta`). You should try out the next steps before the PR on devnet first, but switch to mainnet for the actual release. - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. - Authorize all [currently existing solver](https://app.notion.com/p/cownation/Solvers-for-Solana-Dev-Contracts-3ca8da5f04ca80968642e85640178cbd) using the solver CLI (`cow solver add --help`). - Create a PR with the changes and wait for approval. From 9c00f316e1f08028c842a5f6f79b149d584dac52 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:21:33 +0200 Subject: [PATCH 11/15] Add gitignore --- .gitignore | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.gitignore b/.gitignore index c812024..fb4f40a 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,9 @@ /target proptest-regressions/ .cargo-root/ + +# Make sure no Solana key is uploaded by accident. +*.json +!bench-report.json +!programs/settlement/cu-report.json +!programs/settlement/idl/** From 81802157cfe6f2ecf4f477cab1d1ca1704a5430a Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:27:54 +0200 Subject: [PATCH 12/15] Create release --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index c956abd..55f54fc 100644 --- a/README.md +++ b/README.md @@ -139,6 +139,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Authorize all [currently existing solver](https://app.notion.com/p/cownation/Solvers-for-Solana-Dev-Contracts-3ca8da5f04ca80968642e85640178cbd) using the solver CLI (`cow solver add --help`). - Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). +- Create a [new GitHub release](https://github.com/cowprotocol/solana-programs/releases/new); in doing so, create a new tag like `v0.42`; title "Alpha release, v0.42". ### Patch update From 76e64b27cd7834aa109d90d045550f0b2a4dcd54 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:31:12 +0200 Subject: [PATCH 13/15] Add instructions on how to test that the packages would work --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 55f54fc..0439405 100644 --- a/README.md +++ b/README.md @@ -137,6 +137,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Switch your network to mainnet (`solana config set --url mainnet-beta`). You should try out the next steps before the PR on devnet first, but switch to mainnet for the actual release. - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. - Authorize all [currently existing solver](https://app.notion.com/p/cownation/Solvers-for-Solana-Dev-Contracts-3ca8da5f04ca80968642e85640178cbd) using the solver CLI (`cow solver add --help`). +- Make sure the package installs without errors: run `cargo install --locked cow-test-cli` (it depends on all other packages). - Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). - Create a [new GitHub release](https://github.com/cowprotocol/solana-programs/releases/new); in doing so, create a new tag like `v0.42`; title "Alpha release, v0.42". From 1ce725c8ef9e9dbdc825e5bf597d8fb1551f1edb Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:34:25 +0200 Subject: [PATCH 14/15] Specify command for local install --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0439405..e358691 100644 --- a/README.md +++ b/README.md @@ -137,7 +137,7 @@ You can use the settle CLI for a smoke test of the programs after a release. See - Switch your network to mainnet (`solana config set --url mainnet-beta`). You should try out the next steps before the PR on devnet first, but switch to mainnet for the actual release. - [Deploy the programs](#how-to-deploy). The deployer keypair is in 1password (under "Solana Deployer"). The program keypair file is the key that was generated before. - Authorize all [currently existing solver](https://app.notion.com/p/cownation/Solvers-for-Solana-Dev-Contracts-3ca8da5f04ca80968642e85640178cbd) using the solver CLI (`cow solver add --help`). -- Make sure the package installs without errors: run `cargo install --locked cow-test-cli` (it depends on all other packages). +- Make sure the package installs without errors: run `cargo install --path /mnt/lima-solana/repos/solana-programs/solana-program-workbench/test-cli --locked` (it depends on all other packages). - Create a PR with the changes and wait for approval. - [Publish the cargo packages](#publishing-the-cargo-packages). - Create a [new GitHub release](https://github.com/cowprotocol/solana-programs/releases/new); in doing so, create a new tag like `v0.42`; title "Alpha release, v0.42". From 391c16b51d3eb504799c9cd5b7d446da04b7c855 Mon Sep 17 00:00:00 2001 From: Federico Giacon <58218759+fedgiac@users.noreply.github.com> Date: Fri, 28 Aug 2026 18:39:39 +0200 Subject: [PATCH 15/15] Remove unneeded file --- .gitignore | 1 - 1 file changed, 1 deletion(-) diff --git a/.gitignore b/.gitignore index fb4f40a..fcdf628 100644 --- a/.gitignore +++ b/.gitignore @@ -5,5 +5,4 @@ proptest-regressions/ # Make sure no Solana key is uploaded by accident. *.json !bench-report.json -!programs/settlement/cu-report.json !programs/settlement/idl/**