Update ex doc v0.40.3

[garazdawi]

No description provided.

[github-actions]

CT Test Results

    3 files    136 suites   48m 52s ⏱️
1 676 tests 1 620 ✅ 56 💤 0 ❌
2 318 runs  2 244 ✅ 74 💤 0 ❌

Results for commit 704d3f5.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• No Windows Installer found

// Erlang/OTP Github Action Bot

[Mikaka27]

@garazdawi since OTP-29 is released, we need to retarget this to maint-29.

[garazdawi]

You probably want to include the fix for #11109 as well, which means we need to get a new version of ex_doc tagged.

[Mikaka27]

Yea, that one is not released yet. Is there something specific this v0.40.2 is fixing for us since it's not the records stuff?

[garazdawi]

These three:

• Skip HTML comments when computing synopsis elixir-lang/ex_doc#2214
• Fix markdown backend code fence language and opaque type display elixir-lang/ex_doc#2215
• Update makeup_erlang version elixir-lang/ex_doc#2236

The major one being the last one which makes syntax highlighting better and work with native records.

[garazdawi]

If a patch is imminent I can ask José to tag a new release so that we can get the record fix.

[Mikaka27]

The patches are planned for wednesday (27th of may).

[garazdawi]

This PR now updates to 0.40.3 which includes the record autolink fix.

[Mikaka27]

I didn't try to to set base to maint-xx ever, I think it needs to be set to maint (so the PR closes when it's merged to maint and master). I was talking about maint-29, to ensure that the base of the branch is fine for merging into 29, sorry about the confusion.

[garazdawi]

You can change it yourself, but now I’ve changed it to maint.