Incremental Reads always reads the last datetime partition instead of skipping it

[octopyth]

I am following the Low-Code CDK tutorial
https://docs.airbyte.com/connector-development/config-based/tutorial/incremental-reads

At step 5 Incremental Reads,
I set sample_state.json to

{
  "rates": {
    "date": "2024-11-07"
  }
}

when I run

poetry run source-exchange-rates-tutorial read --config secrets/config.json --catalog integration_tests/configured_catalog.json --state integration_tests/sample_state.json

I get

{"type": "STATE", "state": {"type": "STREAM", "stream": {"stream_descriptor": {"name": "rates", "namespace": null}, "stream_state": {"date": "2024-11-07"}}, "sourceStats": {"recordCount": 1.0}}}
{"type": "LOG", "log": {"level": "INFO", "message": "Read 1 records from rates stream"}}
{"type": "LOG", "log": {"level": "INFO", "message": "Marking stream rates as STOPPED"}}

Every time I run the connector it always reads the record for the last date partition, even though it has been already read.
In the tutorial the expected behaviour is to read 0 records

{"type": "STATE", "state": {"type": "STREAM", "stream": {"stream_descriptor": {"name": "rates", "namespace": null}, "stream_state": {"date": "2024-11-07"}}, "sourceStats": {"recordCount": 0.0}}}
{"type": "LOG", "log": {"level": "INFO", "message": "Read 0 records from rates stream"}}

I replicated this behaviour in the No-Code CDK and it always reads the last stream_slice stored in the state.
Am I doing something wrong, or is this behaviour the new normal, considered a feature, not a bug?
Thanks!