How to reflect changes done to proto buf in API reference docs

[ashikjm]

When i regenerated the proto buf, it printed the following. Is this still to be followed? I am not able to find the next folder, so I am assuming the documentation is stale.

Ref Issue : etcd-io/etcd#18267
PR : etcd-io/etcd#19446

The API references have NOT been automatically published on the website.

To publish the API references, copy the following files
  - Documentation/dev-guide/api_reference_v3.md
  - Documentation/dev-guide/api_concurrency_reference_v3.md
to the etcd-io/website repo under the /content/en/docs/next/dev-guide/ folder.
etcdserver: Regenerate protobuf binding
(https://github.com/etcd-io/website/tree/main/content/en/docs/next/dev-guide)

[ivanvc]

Cross posting: etcd-io/etcd#19446 (comment)

The issue is that we don't have a next directory. We have v3.6. But if your pull request targets main, it shouldn't be in v3.6's documentation.

[ahrtr]

I recall the maintainers discussed this a couple of years before, but I lost the context now.

Two questions:

• If we create a next directory, will the content/en/docs/next/dev-guide/ be automatically updated?
• If we backport the etcdserver: Update description for count field in the RangeResponse message etcd#19446 to 3.6, will content/en/docs/v3.6/dev-guide/ be automatically updated?

cc @ivanvc @jmhbnz @serathius @spzala

[ivanvc]

As far as I know, the answer to both questions is no. We'd need to write some automation to update the documentation, but we have been unsuccessful in these tasks because of GitHub permissions.

[ashikjm]

So currently if we have a pull request targetting 3.6 (etcd-io/etcd#19468), do I submit changes in documentation under the 3.6 folder?

[ivanvc]

So currently if we have a pull request targetting 3.6 (etcd-io/etcd#19468), do I submit changes in documentation under the 3.6 folder?

Yes, please. 🙏

[ashikjm]

I found a typo in the etcd v3election protobuf. Will fix that too and raise a single PR.

PR to fix typos : etcd-io/etcd#19498