chore: hard set solc version at 0.8.19 bc of rollup limitations

README.md

@@ -36,7 +36,9 @@ If you are not running Supabase, then the search functionality will not work. Yo
 
 ### Updating bytecode
 
-Whenever you make a change to smart contracts, increment the version by `x.1`. Then generate the bytecode and version it as described below.
+Whenever you make a change to smart contracts or really whenever the bytecode files change (could be that [the compiler version got changed and so no bytecode changed, but remappings were reformatted](https://github.com/jk-labs-inc/jokerace/pull/509)), increment the version by `x.1`. Then generate the bytecode and version it as described below.
+
+The purpose of this is so that we have a way to tell exactly what bytecode a contract that we read from a chain has and exactly how it was deployed given its version number.
 
 In order to generate and/or update the bytecode of your project, run 
 

packages/forge/foundry.toml

@@ -2,5 +2,6 @@
 src = "src"
 out = "out"
 libs = ["lib"]
+solc-version = "0.8.19"  # most rollups don't support past this - https://twitter.com/pashovkrum/status/1690298101448208384?s=46
 
 # See more config options https://github.com/foundry-rs/foundry/tree/master/config

packages/forge/src/governance/Governor.sol

@@ -84,7 +84,7 @@ abstract contract Governor is Context, ERC165, EIP712, GovernorMerkleVotes, IGov
      * @dev See {IGovernor-version}.
      */
     function version() public view virtual override returns (string memory) {
-        return "3.2";
+        return "3.3";
     }
 
     /**

packages/forge/src/modules/RewardsModule.sol

@@ -90,7 +90,7 @@ contract RewardsModule is Context {
      * @dev Version of the rewards module. Default: "1"
      */
     function version() public view virtual returns (string memory) {
-        return "3.2";
+        return "3.3";
     }
 
     /**

packages/react-app-revamp/README.md

@@ -36,7 +36,9 @@ If you are not running Supabase, then the search functionality will not work. Yo
 
 ### Updating bytecode
 
-Whenever you make a change to smart contracts, increment the version by `x.1`. Then generate the bytecode and version it as described below.
+Whenever you make a change to smart contracts or really whenever the bytecode files change (could be that [the compiler version got changed and so no bytecode changed, but remappings were reformatted](https://github.com/jk-labs-inc/jokerace/pull/509)), increment the version by `x.1`. Then generate the bytecode and version it as described below.
+
+The purpose of this is so that we have a way to tell exactly what bytecode a contract that we read from a chain has and exactly how it was deployed given its version number.
 
 In order to generate and/or update the bytecode of your project, run