Publish javadoc for Robolectric 4.12.2

[github-actions]

• Add javadoc for Robolectric 4.12.2.

• Update mkdocs.yml to add a navigation entry to the new javadoc.

• Update mkdocs.yml to use version 4.12.2.

Fixes #2382144206

[MGaetan89]

@utzcoz @hoisie here's a PR created from the publish-javadoc workflow.

I see that the Fixes #xxx in the PR description points to the wrong issue. I'll send a PR to fix that.
If you notice something else that's wrong or could be improved, let me know, and I'll address it too.

[utzcoz]

@MGaetan89 Looks like it replaces the 4.12 directory instead of a new directory.

[MGaetan89]

@MGaetan89 Looks like it replaces the 4.12 directory instead of a new directory.

I thought that was the expected behaviour. But what you want is to have one folder per version, even for patch releases, right?
So we'd have a 4.12 folder, as well as a 4.12.2 folder?

If so, does it mean that in the menu, we have an entry for both 4.12 and 4.12.2?

[utzcoz]

So we'd have a 4.12 folder, as well as a 4.12.2 folder?

Yeah. Every version should have it separate directory. There might have some minor API changes between main version and patch version.

[utzcoz]

Let's check whether the approve can make CI continue for this PR.

[utzcoz]

Looks like CI doesn't work as expected.

[utzcoz]

https://github.com/orgs/community/discussions/55906 Looks like it is related to GITHUB_TOKEN.

[MGaetan89]

So we'd have a 4.12 folder, as well as a 4.12.2 folder?

Yeah. Every version should have it separate directory. There might have some minor API changes between main version and patch version.

Got it, I'll update the workflow accordingly. It'll make things easier then.

github.com/orgs/community/discussions/55906 Looks like it is related to GITHUB_TOKEN.

Thanks for the link. So we need a dedicated token to be created and added to this repository setting, so we can use it in the workflow, right?

[utzcoz]

So we need a dedicated token to be created and added to this repository setting, so we can use it in the workflow, right?

From the discussion, I think yes. We can move to discuss it to Slack, and check whether we can add a special token for it or we have other approaches.

[MGaetan89]

Closing this PR, as a new version will be submitted once #264 is merged.