Updated repository pin in the docs

[UebelAndre]

I don't think we need to update the pin for every release but 0.1.0 had some things missing from the release artifact so I think it'd be good to move to 0.2.0 where this is fixed.

[hlopko]

I don't mind this PR, but to me as a reader 0.1.0 would clearly signal that I should look elsewhere for the up to date information (and that elsewhere would be GitHub releases). With 0.2.0 I'd be a little bit more confused (is it really just 0.2.0 or is this obsolete?).

We can consider updating docs on each release. Or even build and release docs with each release (that way we would have versioned docs).

Anyway, I don't feel strongly, hence approved :)

[UebelAndre]

I don't mind this PR, but to me as a reader 0.1.0 would clearly signal that I should look elsewhere for the up to date information (and that elsewhere would be GitHub releases). With 0.2.0 I'd be a little bit more confused (is it really just 0.2.0 or is this obsolete?).

We can consider updating docs on each release. Or even build and release docs with each release (that way we would have versioned docs).

Anyway, I don't feel strongly, hence approved :)

Thanks! Ideally I think there should be docs for each release and ones tracking main. This way we don't have to worry about the pins for older releases and the docs tracking main can have stronger guidance.