From cad17d0648c6e1cb100998999471843e2938bb91 Mon Sep 17 00:00:00 2001 From: Ryan Sauge <71391932+rya-sge@users.noreply.github.com> Date: Fri, 15 Aug 2025 12:52:59 +0200 Subject: [PATCH] change release name --- CHANGELOG.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a37ec0d..6ed0e92 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,10 +17,9 @@ Please follow [https://changelog.md/](https://changelog.md/) conventions. - Update surya doc by running the 3 scripts in [./doc/script](./doc/script) - Update changelog -## v3.0.0-rc1 +## v3.0.0-rc0 - Rule contracts, requires to perform compliance check, have now their own dedicated [GitHub repository](https://github.com/CMTA/Rules). It means that these contract will be developed and audited separately from the `RuleEngine`. This provides more flexibility and makes it easier to manage audits. - - There is now only one type of rule (read-write rules). Before that: - First RuleEngine version (audited) had only one type of rule, read-only (whitelist, blacklist) - A second RuleEngine version (not audited) had two types of rules: operation (read-write) and validation (read-only). A read-write rule is typically a ConditionalTransfer check which require each transfer must be pre-approved. @@ -31,11 +30,6 @@ Please follow [https://changelog.md/](https://changelog.md/) conventions. - `RuleEngineOperation`-> `RulesManagementModule` - `MetaTxModuleStandalone` -> `ERC2771ModuleStandalone` -## v3.0.0-rc0 - -- Improve test -- Move rules contracts to a dedicated repository, only keep some rules as mock contracts for testing purpose - ## v2.1.0 - Update RuleEngine to CMTAT v3.0.0-rc5