MIME-Version: 1.0
References: <3ydjipcr7kbss57nvi67noplncqhesl5eyb6wgol4ccjxynspv@yatlykpribmm>
 <DIM49A100EY1.2YFS2A6WAI3ZJ@jeltef.nl>
 <CAN55FZ30Np67cATsqYxF1SsP598VoRv4hJQZ4w9RA3Qe55prnQ@mail.gmail.com>
 <CAN55FZ13uX0cLSbgtSnnFeh5sTLeMr7+8UzmqpU6QjOtrRJTLg@mail.gmail.com>
 <qe4lh2i5di2gh7bxkbfisifaohrvyfukbybwxwzxdnll45hnt3@luod7i2mon67>
 <CAN55FZ1-qiOWtQH5o6Q_7LJ7S3Ef_hfDE068uP0hGjB3gzwghg@mail.gmail.com>
In-Reply-To: 
 <CAN55FZ1-qiOWtQH5o6Q_7LJ7S3Ef_hfDE068uP0hGjB3gzwghg@mail.gmail.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Thu, 28 May 2026 13:50:26 -0700
Message-ID: 
 <CAOYmi+kB4Tv8-iVvJK=+8xrPdKZ=bq==gXR2rOHr1wM8TVzPnw@mail.gmail.com>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Andres Freund <andres@anarazel.de>,
 Jelte Fennema-Nio <postgres@jeltef.nl>,
	Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@postgresql.org,
	Zsolt Parragi <zsolt.parragi@percona.com>,
 Peter Eisentraut <peter@eisentraut.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAOYmi%2BkB4Tv8-iVvJK%3D%2B8xrPdKZ%3Dbq%3D%3DgXR2rOHr1wM8TVzPnw%40mail.gmail.com>
Precedence: bulk

On Thu, May 28, 2026 at 10:06=E2=80=AFAM Nazir Bilal Yavuz <byavuz81@gmail.=
com> wrote:
> > > +          $prefix =3D (python -c "import sys; print(sys.prefix)").Tr=
im()
> > > +          Add-Content $env:GITHUB_ENV "PYTHONHOME=3D$prefix"
> > > +          Add-Content $env:GITHUB_PATH $prefix
> > > +          Write-Host "PYTHONHOME=3D$prefix"
> > > +          Write-Host "Prepended $prefix to PATH"
> >
> > GRJGJKLJKJDFJKDF.
>
> I re-checked this since Jelte wasn't completely sure about this [2]
> but this is unfortunately correct :(

What are the chances we can strip Mercurial out of the PATH instead of
messing with PYTHONHOME? I foresee pain in the future if we override
that globally.

> v3 is attached.

> +        uses: msys2/setup-msys2@v2

Should we pin this? It's the only third-party action we reference, and
Scorecard [1] complains. (I'm not convinced its other complaints in
this category are something we want to worry about, but this caught my
eye.)

We'd need to figure out how to keep it up to date, if we pinned it.
But we probably need to figure out how to keep it up to date anyway.

Scorecard doesn't report any `Dangerous-Workflow` violations, so that's goo=
d.

--Jacob

[1] https://scorecard.dev/