我目前正在运行consul 1.0.3并将其与spring-cloud 1.3.3一起使用。 在consul文档中，它表示从consul 1.0.6升级到更高版本时可能会有重大变化：
Upgrade from Version 1.0.6 to higher
In version 1.0.7 and higher, when requesting a specific service
(/v1/health/:service or /v1/catalog/:service endpoints), the X-Consul-Index
returned is now the index at which that specific service was last modified.
In version 1.0.6 and earlier the X-Consul-Index returned was the index at
which any service was last modified. See GH-3890 for more details.
During upgrades from 1.0.6 or lower to 1.0.7 or higher, watchers are likely
to
see X-Consul-Index for these endpoints decrease between blocking calls.
Consul’s watch feature and consul-template should gracefully handle this
case. Other tools relying on blocking service or health queries are also
likely to work; some may require a restart. It is possible external tools
could break and either stop working or continually re-request data without
blocking if they have assumed indexes can never decrease or be reset and/or
persist index values. Please test any blocking query integrations in a
controlled environment before proceeding.
Spring-cloud 1.3.3受此影响了吗？是否在文档的某处说明了哪些版本的consul兼容？
谢谢， 约翰内斯