Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce a blocklist of "yanked" Postgres versions #1950

Merged
merged 11 commits into from
Nov 22, 2024
Merged

Introduce a blocklist of "yanked" Postgres versions #1950

merged 11 commits into from
Nov 22, 2024

Commits on Nov 22, 2024

  1. Introduce a blocklist of "yanked" Postgres versions 

    Due to the out-of-band release set described here:
https://www.postgresql.org/about/news/postgresql-172-166-1510-1415-1318-and-1222-released-2965/,
we should refuse to compile on the prior point releases mentioned in
this press release.
    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    a70b33c View commit details
    Browse the repository at this point in the history

  2. take a slightly different approach with the code

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    082c3d7 View commit details
    Browse the repository at this point in the history

  3. report postgres version

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    6231e3e View commit details
    Browse the repository at this point in the history

  4. could this be the problem?

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    ae820df View commit details
    Browse the repository at this point in the history

  5. nope

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    5ee556a View commit details
    Browse the repository at this point in the history

  6. lets try this...

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    1e351c5 View commit details
    Browse the repository at this point in the history

  7. nope

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    4f84598 View commit details
    Browse the repository at this point in the history

  8. use the official postgres apt repo

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    7643784 View commit details
    Browse the repository at this point in the history

  9. come on CI, do the things

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    45e0621 View commit details
    Browse the repository at this point in the history

  10. use the official postgres apt repo

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    f003171 View commit details
    Browse the repository at this point in the history

  11. why is CI so damn painful? YAML is terrible is one reason

    @eeeebbbbrrrr
    eeeebbbbrrrr committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    b35eb96 View commit details
    Browse the repository at this point in the history