Re: Unicode update and some tooling improvements

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Chao Li <li.evan.chao@gmail.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2026-03-02T07:29:52Z

Lists: pgsql-hackers

On 27.02.26 03:50, Chao Li wrote:
> Only a small comment on 0003:
> ```
>     # Meson 0.57.0 and 0.57.1 are buggy, therefore >=0.57.2.
> -  meson_version: '>=0.57.2',
> +  # FIXME: update comment
> +  meson_version: '>=0.58',
> ```
> 
> Why leaves a FIXME instead of just updating the comment? I saw the installation.sgml doc has been updated.

It wasn't meant to be committed that way.  I just didn't want to spend 
the time crafting a comment before it was generally agreed to proceed in 
this way that required a meson version update.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Update Unicode data to CLDR 48.2
- b47854b6992d 19 (unreleased) landed
Update Unicode data to Unicode 17.0.0
- 57ee39795398 19 (unreleased) landed
Update RELEASE_CHANGES
- 9b406a9e4854 19 (unreleased) landed
Implement unaccent Unicode data update in meson
- 1b0c269f2e4f 19 (unreleased) landed
doc: Fix capitalization of Unicode
- 90ca7c1429d6 19 (unreleased) landed
Fix Python deprecation warning
- 16686a853f1b 19 (unreleased) landed