fix feature propagation

Author: orriin

node/Cargo.toml

@@ -119,8 +119,12 @@ rocksdb = [
 	"sc-service/rocksdb",
 	"fc-db/rocksdb",
 	"fc-mapping-sync/rocksdb",
+	"fc-rpc/rocksdb"
+]
+txpool = [
+	"fc-rpc/txpool",
+	"fc-rpc-core/txpool"
 ]
-txpool = ["fc-rpc/txpool"]
 
 # Dependencies that are only required if runtime benchmarking should be build.
 runtime-benchmarks = [

zepter.yaml

@@ -12,13 +12,13 @@ workflows:
         # Check that `A` activates the features of `B`.
         "propagate-feature",
         # These are the features to check:
-        "--features=try-runtime,runtime-benchmarks,std",
+        "--features=try-runtime,runtime-benchmarks,std,sql,rocksdb,txpool",
         # Do not try to add a new section into `[features]` of `A` only because `B` expose that feature. There are edge-cases where this is still needed, but we can add them manually.
         "--left-side-feature-missing=ignore",
         # Ignore the case that `A` it outside of the workspace. Otherwise it will report errors in external dependencies that we have no influence on.
         "--left-side-outside-workspace=ignore",
         # Some features imply that they activate a specific dependency as non-optional. Otherwise the default behaviour with a `?` is used.
-        "--feature-enables-dep=try-runtime:frame-try-runtime,runtime-benchmarks:frame-benchmarking",        # Auxillary flags:
+        "--feature-enables-dep=try-runtime:frame-try-runtime,runtime-benchmarks:frame-benchmarking", # Auxillary flags:
         "--offline",
         "--locked",
         "--show-path",