chore: remove unused batching contract (#279)

.github/workflows/release.yaml

@@ -9,7 +9,6 @@ on:
         options:
           - ampd
           - agggregate-verifier
-          - batching
           - connection-router
           - gateway
           - multisig
@@ -41,7 +40,6 @@ jobs:
           declare -A binaries_data=(
             ["ampd"]="ampd,major-ampd,minor-ampd,"
             ["aggregate-verifier"]="aggregate-verifier,/(major-aggregate-verifier)|(major-contracts)/,/(minor-aggregate-verifier)|(minor-contracts)/,contracts/aggregate-verifier packages"
-            ["batching"]="batching,/(major-batching)|(major-contracts)/,/(minor-batching)|(minor-contracts)/,contracts/batching packages"
             ["connection-router"]="connection-router,/(major-connection-router)|(major-contracts)/,/(minor-connection-router)|(minor-contracts)/,contracts/connection-router packages"
             ["gateway"]="gateway,/(major-gateway)|(major-contracts)/,/(minor-gateway)|(minor-contracts)/,contracts/gateway packages"
             ["multisig"]="multisig,/(major-multisig)|(major-contracts)/,/(minor-multisig)|(minor-contracts)/,contracts/multisig packages"

README.md

@@ -19,4 +19,4 @@ When developing contracts to integrate with amplifier, the `cw-multi-test` crate
 The semver for new releases is calculated automatically based on the commit messages and the folders where changes were made. The configuration for each piece of software released (e.g ampd, gateway...) can be seen in the release.yaml file. You can perform a dry-run using the release action to be sure that the next version is what you intend it to be. The basic rules are as follows:
  - a commit with a message that does not include any associated tag (e.g major-contracts) for release will be considered a patch release
  - a commit with a message with minor tag e.g `feat(minor-ampd):...` will be considered a minor release, and the same logic applies to major releases
- - if no changes are detected in the watched directories, the release will not bump the version. e.g if since last release for the batching contract, no changes were made in the `contracts/major-batching` or `packages/` directory. A new release will not bump the version.
+ - if no changes are detected in the watched directories, the release will not bump the version. For example, if since last release for the gateway contract no changes were made in the `contracts/gateway` or `packages/` directory. A new release will not bump the version.