Because vector tile docs are pegged to released versions, we either need to wait until v1.0 goes live or back-port those docs changes to a new branch based on the v0.10.2 tag (and then in docs maker we’d peg to that SHA).
The unified key changes are in master, although we can roll back https://github.com/tilezen/vector-datasource/pull/1051 if there is too much jumble between these changes and other functions that are only in v1 and we want to get the docs out sooner.
rmglennon
commented
8 years ago
There are documentation updates in https://github.com/tilezen/vector-datasource to consider the unified key.
The documentation makefile is pointing to https://github.com/tilezen/vector-datasource/archive/v0.10.2.tar.gz right now, so only includes content up to 0.10.2.
Because vector tile docs are pegged to released versions, we either need to wait until v1.0 goes live or back-port those docs changes to a new branch based on the v0.10.2 tag (and then in docs maker we’d peg to that SHA).
The unified key changes are in master, although we can roll back https://github.com/tilezen/vector-datasource/pull/1051 if there is too much jumble between these changes and other functions that are only in v1 and we want to get the docs out sooner.