Bump version to 0.12.0

rkalis · rkalis · commit fac75431720a · 2025-10-02T11:59:46.000+02:00
diff --git a/examples/announcement.cash b/examples/announcement.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 /* This is a contract showcasing covenants outside of regular transactional use.
  * It enforces the contract to make an "announcement" on Memo.cash, and send the
diff --git a/examples/hodl_vault.cash b/examples/hodl_vault.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 // This contract forces HODLing until a certain price target has been reached
 // A minimum block is provided to ensure that oracle price entries from before this block are disregarded
diff --git a/examples/mecenas.cash b/examples/mecenas.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 /* This is an unofficial CashScript port of Licho's Mecenas contract. It is
  * not compatible with Licho's EC plugin, but rather meant as a demonstration
diff --git a/examples/mecenas_locktime.cash b/examples/mecenas_locktime.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 // This is an experimental contract for a more "streaming" Mecenas experience
 // Completely untested, just a concept
diff --git a/examples/p2pkh.cash b/examples/p2pkh.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract P2PKH(bytes20 pkh) {
     // Require pk to match stored pkh and signature to match
diff --git a/examples/package.json b/examples/package.json
@@ -1,7 +1,7 @@
 {
   "name": "cashscript-examples",
   "private": true,
-  "version": "0.11.5",
+  "version": "0.12.0",
   "description": "Usage examples of the CashScript SDK",
   "main": "p2pkh.js",
   "type": "module",
@@ -13,8 +13,8 @@
   "dependencies": {
     "@bitauth/libauth": "^3.1.0-next.2",
     "@types/node": "^22.17.0",
-    "cashc": "^0.11.5",
-    "cashscript": "^0.11.5",
+    "cashc": "^0.12.0",
+    "cashscript": "^0.12.0",
     "eslint": "^8.56.0",
     "typescript": "^5.9.2"
   }
diff --git a/examples/testing-suite/package.json b/examples/testing-suite/package.json
@@ -1,6 +1,6 @@
 {
   "name": "testing-suite",
-  "version": "0.11.5",
+  "version": "0.12.0",
   "description": "Example project to develop and test CashScript contracts",
   "main": "index.js",
   "type": "module",
@@ -26,8 +26,8 @@
   },
   "dependencies": {
     "@bitauth/libauth": "^3.1.0-next.2",
-    "cashc": "^0.11.5",
-    "cashscript": "^0.11.5",
+    "cashc": "^0.12.0",
+    "cashscript": "^0.12.0",
     "url-join": "^5.0.0"
   },
   "devDependencies": {
diff --git a/examples/transfer_with_timeout.cash b/examples/transfer_with_timeout.cash
@@ -1,4 +1,4 @@
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract TransferWithTimeout(
     pubkey sender,
diff --git a/packages/cashc/package.json b/packages/cashc/package.json
@@ -1,6 +1,6 @@
 {
   "name": "cashc",
-  "version": "0.11.5",
+  "version": "0.12.0",
   "description": "Compile Bitcoin Cash contracts to Bitcoin Cash Script or artifacts",
   "keywords": [
     "bitcoin",
@@ -52,7 +52,7 @@
   },
   "dependencies": {
     "@bitauth/libauth": "^3.1.0-next.8",
-    "@cashscript/utils": "^0.11.5",
+    "@cashscript/utils": "^0.12.0",
     "antlr4": "^4.13.2",
     "commander": "^14.0.0",
     "semver": "^7.7.2"
diff --git a/packages/cashc/src/index.ts b/packages/cashc/src/index.ts
@@ -2,4 +2,4 @@ export * from './Errors.js';
 export * as utils from '@cashscript/utils';
 export { compileFile, compileString } from './compiler.js';
 
-export const version = '0.11.5';
+export const version = '0.12.0';
diff --git a/packages/cashscript/package.json b/packages/cashscript/package.json
@@ -1,6 +1,6 @@
 {
   "name": "cashscript",
-  "version": "0.11.5",
+  "version": "0.12.0",
   "description": "Easily write and interact with Bitcoin Cash contracts",
   "keywords": [
     "bitcoin cash",
@@ -46,7 +46,7 @@
   },
   "dependencies": {
     "@bitauth/libauth": "^3.1.0-next.8",
-    "@cashscript/utils": "^0.11.5",
+    "@cashscript/utils": "^0.12.0",
     "@electrum-cash/network": "^4.1.3",
     "@mr-zwets/bchn-api-wrapper": "^1.0.1",
     "pako": "^2.1.0",
diff --git a/packages/utils/package.json b/packages/utils/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@cashscript/utils",
-  "version": "0.11.5",
+  "version": "0.12.0",
   "description": "CashScript utilities and types",
   "keywords": [
     "bitcoin cash",
diff --git a/website/docs/basics/getting-started.md b/website/docs/basics/getting-started.md
@@ -52,7 +52,7 @@ We can start from a basic `TransferWithTimeout` smart contract, a simple contrac
 
 Open your code editor to start writing your first CashScript smart contract. Then create a new file `TransferWithTimeout.cash` and copy over the smart contracts code from below.
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract TransferWithTimeout(pubkey sender, pubkey recipient, int timeout) {
     // Allow the recipient to claim their received money
diff --git a/website/docs/language/contracts.md b/website/docs/language/contracts.md
@@ -13,7 +13,7 @@ Contract authors should be careful when allowing a range of versions to check th
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 pragma cashscript >= 0.7.0 < 0.9.3;
 ```
 
@@ -22,7 +22,7 @@ A CashScript constructor works slightly differently than what you might be used
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract HTLC(pubkey sender, pubkey recipient, int expiration, bytes32 hash) {
     ...
@@ -46,7 +46,7 @@ The main construct in a CashScript contract is the function. A contract can cont
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract TransferWithTimeout(pubkey sender, pubkey recipient, int timeout) {
     function transfer(sig recipientSig) {
@@ -89,7 +89,7 @@ The error message in a `require` statement is only available in debug evaluation
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract P2PKH(bytes20 pkh) {
     function spend(pubkey pk, sig s) {
@@ -131,7 +131,7 @@ There is no implicit type conversion from non-boolean to boolean types. So `if (
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract OneOfTwo(bytes20 pkh1, bytes32 hash1, bytes20 pkh2, bytes32 hash2) {
     function spend(pubkey pk, sig s, bytes message) {
@@ -158,7 +158,7 @@ Logging is only available in debug evaluation of a transaction, but has no impac
 
 #### Example
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract P2PKH(bytes20 pkh) {
     function spend(pubkey pk, sig s) {
diff --git a/website/docs/language/examples.md b/website/docs/language/examples.md
@@ -12,7 +12,7 @@ This smart contract works by connecting with a price oracle. This price oracle i
 This involves some degree of trust in the price oracle, but since the oracle produces price data for everyone to use, their incentive to attack *your* smart contract is minimised. To improve this situation, you can also choose to connect with multiple oracle providers so you do not have to trust a single party.
 
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 // A minimum block is provided to ensure that oracle price entries from before
 // this block are disregarded. i.e. when the BCH price was $1000 in the past,
@@ -53,7 +53,7 @@ The contract works by checking that a UTXO is at least 30 days old, after which
 Due to the nature of covenants, we have to be very specific about the outputs (amounts and destinations) of the transaction. This also means that we have to account for the special case where the remaining contract balance is lower than the `pledge` amount, meaning no remainder should be sent back. Finally, we have to account for a small fee that has to be taken from the contract's balance to pay the miners.
 
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract Mecenas(bytes20 recipient, bytes20 funder, int pledge, int period) {
     function receive() {
@@ -95,7 +95,7 @@ AMM DEX contract based on [the Cauldron DEX contract](https://www.cauldron.quest
 The CashScript contract code has the big advantage of abstracting away any stack management, having variable names, explicit types and a logical order of operations (compared to the 'reverse Polish notation' of raw script).
 
 ```solidity
-pragma cashscript ^0.11.0;
+pragma cashscript ^0.12.0;
 
 contract DexContract(bytes20 poolOwnerPkh) {
     function swap() {

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-pragma cashscript ^0.11.0;`
	`1`	`+pragma cashscript ^0.12.0;`
`2`	`2`
`3`	`3`	`/* This is a contract showcasing covenants outside of regular transactional use.`
`4`	`4`	`* It enforces the contract to make an "announcement" on Memo.cash, and send the`