docs: update release notes for timestamp filtering

Author: darioAnongba

cmd/commands/addrs.go

@@ -284,12 +284,14 @@ var receivesAddrCommand = cli.Command{
 			Usage: "show transfers of a single address only",
 		},
 		cli.Uint64Flag{
-			Name:  "start_timestamp",
-			Usage: "filter transfers created after this unix timestamp (seconds)",
+			Name: "start_timestamp",
+			Usage: "filter transfers created after this + " +
+				"unix timestamp (seconds)",
 		},
 		cli.Uint64Flag{
-			Name:  "end_timestamp",
-			Usage: "filter transfers created before this unix timestamp (seconds)",
+			Name: "end_timestamp",
+			Usage: "filter transfers created before this + " +
+				"unix timestamp (seconds)",
 		},
 	},
 	Action: addrReceives,

docs/release-notes/release-notes-0.7.0.md

@@ -168,6 +168,9 @@
   user to specify a custom amount to send to a V2 address that doesn't have an
   amount specified.
 
+- The `AddrReceives` RPC now supports timestamp filtering with
+  [new `StartTimestamp` and `EndTimestamp` fields](https://github.com/lightninglabs/taproot-assets/pull/1794).
+
 ## tapcli Additions
 
 - [Rename](https://github.com/lightninglabs/taproot-assets/pull/1682) the mint
@@ -186,6 +189,9 @@
   includes unset and zero-valued proto fields (e.g. transaction output indexes).
   This ensures consistent output shape across all proto messages.
 
+- The `tapcli addrs receives` command now supports 
+  [new `--start_timestamp` and `--end_timestamp` flags](https://github.com/lightninglabs/taproot-assets/pull/1794).
+
 # Improvements
 
 ## Functional Updates

itest/addrs_test.go

@@ -1011,17 +1011,6 @@ func testAddrReceives(t *harnessTest) {
 	)
 	require.NoError(t.t, err)
 	require.Len(t.t, resp.Events, 1)
-
-	// Test 10: Filter by both start and end timestamp with narrow range
-	// (should return no events)
-	resp, err = bob.AddrReceives(
-		ctxt, &taprpc.AddrReceivesRequest{
-			StartTimestamp: uint64(timeAfterSend.Unix()),
-			EndTimestamp:   uint64(timeAfterSend.Unix()),
-		},
-	)
-	require.NoError(t.t, err)
-	require.Len(t.t, resp.Events, 0)
 }
 
 // sendProof manually exports a proof from the given source node and imports it