Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id CAOYmi+kB4Tv8-iVvJK=+8xrPdKZ=bq==gXR2rOHr1wM8TVzPnw@mail.gmail.com
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Heads Up: cirrus-ci is shutting down June 1st
Re: Heads Up: cirrus-ci is shutting down June 1st
List pgsql-hackers
On Thu, May 28, 2026 at 10:06 AM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> > > +          $prefix = (python -c "import sys; print(sys.prefix)").Trim()
> > > +          Add-Content $env:GITHUB_ENV "PYTHONHOME=$prefix"
> > > +          Add-Content $env:GITHUB_PATH $prefix
> > > +          Write-Host "PYTHONHOME=$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 good.

--Jacob

[1] https://scorecard.dev/



pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Re: Fix mismatched deallocation functions
Next
From: Álvaro Herrera
Date:
Subject: Re: [PATCH] Improve REPACK (CONCURRENTLY) error messages for unsupported configurations