CRAN release v2.0.2

[krlmlr]

Pre-release checks

• Review CRP last edited {{{ crp_date }}}.
  {{{ crp_changes }}}
• Check on win-builder, R devel
• Review PR
  {{{ check_cran_comments }}}

Action items

• Run fledge::release(){{{ fledge_gha_workflow_release }}}
• Confirm CRAN e-mail
• When the package is accepted on CRAN, run fledge::post_release(){{{ fledge_gha_workflow_release }}}

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[szhorvat]

IMO this should be removed from NEWS because it fixed an issue introduced after 2.0.1.1 was released:

shortest.paths() no longer fails (#1222).

---

It would be good to put this close to the top and rephrase it so that people who were affected by it will understand it:

configure manage libxml multiple include paths (#1197).

I suggest something like "Fixed invalid quoting of libxml2 include paths".

---

Great to see this release! This is the "real 2.0", the first truly usable one.

[krlmlr]

Can you please point me to the hash of the C core you used for the last update? The script tools/update-cigraph.sh includes this info in the commit message.

[szhorvat]

Good point, I'll leave the commit hash in the commit message next time.

It is fd3b8a6b49c2692a4118efda6050c5efb13e827b

We did deprecate (= rename) a function since then, so do not update the C core to the latest before the R release. There are no relevant fixes to pick up.

The renaming will be easy to adapt to later. In fact now the function name matches between R and C, while previously it didn't.