f Move lightning-transaction-sync out of workspace

.. not sure we want to do this, but including it anyways.

Author: tnull

Cargo.toml

@@ -13,14 +13,14 @@ members = [
     "lightning-background-processor",
     "lightning-rapid-gossip-sync",
     "lightning-custom-message",
-    "lightning-transaction-sync",
     "lightning-macros",
     "lightning-dns-resolver",
     "lightning-liquidity",
     "possiblyrandom",
 ]
 
 exclude = [
+    "lightning-transaction-sync",
     "no-std-check",
     "msrv-no-dev-deps-check",
     "bench",

ci/ci-tx-sync-tests.sh

@@ -3,6 +3,8 @@ set -eox pipefail
 
 RUSTC_MINOR_VERSION=$(rustc --version | awk '{ split($2,a,"."); print a[2] }')
 
+pushd lightning-transaction-sync
+
 # Some crates require pinning to meet our MSRV even for our downstream users,
 # which we do here.
 # Further crates which appear only as dev-dependencies are pinned further down.
@@ -18,18 +20,20 @@ PIN_RELEASE_DEPS # pin the release dependencies
 export RUST_BACKTRACE=1
 
 echo -e "\n\nChecking Transaction Sync Clients with features."
-cargo check -p lightning-transaction-sync --verbose --color always --features esplora-blocking
-cargo check -p lightning-transaction-sync --verbose --color always --features esplora-async
-cargo check -p lightning-transaction-sync --verbose --color always --features esplora-async-https
-cargo check -p lightning-transaction-sync --verbose --color always --features electrum
+cargo check --verbose --color always --features esplora-blocking
+cargo check --verbose --color always --features esplora-async
+cargo check --verbose --color always --features esplora-async-https
+cargo check --verbose --color always --features electrum
 
 if [ -z "$CI_ENV" ] && [[ -z "$BITCOIND_EXE" || -z "$ELECTRS_EXE" ]]; then
 	echo -e "\n\nSkipping testing Transaction Sync Clients due to BITCOIND_EXE or ELECTRS_EXE being unset."
-	cargo check -p lightning-transaction-sync --tests
+	cargo check --tests
 else
 	echo -e "\n\nTesting Transaction Sync Clients with features."
-	cargo test -p lightning-transaction-sync --verbose --color always --features esplora-blocking
-	cargo test -p lightning-transaction-sync --verbose --color always --features esplora-async
-	cargo test -p lightning-transaction-sync --verbose --color always --features esplora-async-https
-	cargo test -p lightning-transaction-sync --verbose --color always --features electrum
+	cargo test --verbose --color always --features esplora-blocking
+	cargo test --verbose --color always --features esplora-async
+	cargo test --verbose --color always --features esplora-async-https
+	cargo test --verbose --color always --features electrum
 fi
+
+popd

lightning-transaction-sync/Cargo.toml

@@ -37,5 +37,11 @@ tokio = { version = "1.35.0", features = ["macros"] }
 [target.'cfg(not(target_os = "windows"))'.dev-dependencies]
 electrsd = { version = "0.28.0", default-features = false, features = ["legacy"] }
 
-[lints]
-workspace = true
+[lints.rust.unexpected_cfgs]
+level = "forbid"
+# When adding a new cfg attribute, ensure that it is added to this list.
+#
+# Note that Cargo automatically declares corresponding cfgs for every feature
+# defined in the member-level [features] tables as "expected".
+check-cfg = [
+]