Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1unypE-00DsvP-DY for pgsql-www@arkaria.postgresql.org; Mon, 18 Aug 2025 12:18:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1unypD-00GI0s-NO for pgsql-www@arkaria.postgresql.org; Mon, 18 Aug 2025 12:18:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1unypD-00GI0k-IX for pgsql-www@lists.postgresql.org; Mon, 18 Aug 2025 12:18:56 +0000 Received: from mail-pf1-x42d.google.com ([2607:f8b0:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1unypB-000SoM-1b for pgsql-www@lists.postgresql.org; Mon, 18 Aug 2025 12:18:54 +0000 Received: by mail-pf1-x42d.google.com with SMTP id d2e1a72fcca58-76e1ff326bbso3745194b3a.1 for ; Mon, 18 Aug 2025 05:18:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755519533; x=1756124333; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ae0FuRxoXOHIalIpfUYYdEWGVoa5bCt7c1HiUc99cRY=; b=jvEF92Cvu84v4mpDLmOk805mLn3hIK825vSlRUJS+BE6OQUXbFF7POiLc13/uAz3BG bpfxy4Xodj504CEz1QQfTwhX9Ki8NKOicgxMkRkyXQdqCAjsqf59eHBXKAEDZu7Myu6R VcHciq8L4aeqwOPUQpZPz1/SU5qbNvL+E++KYqThvNt6rDMfTDxeo6dNmcvHRnKXjjSn /jdpqjfE+51OojrEFO26/P5pXXa44f8GnEH0V37aU0xZmOSOBBO16OFTwLvtAg2DifT6 q2kAqysjdY+wDtMpUsSHM8mN1uDVUg0nzrvaqv0aP1QGgmTUluC8fk55NQ9HJfJhsxzm dlmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755519533; x=1756124333; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ae0FuRxoXOHIalIpfUYYdEWGVoa5bCt7c1HiUc99cRY=; b=UL4MaXRT/hk5QMCUfzRAIuZTWwqLIa1FcwPoSniAKvdUOeQcXCFuLTGHQGog/x1kms rkeVmXvkE195hmf51PyYyNQN34eGlBPqN7TG2HWK8FKkld1qvvJf3oSKFB5V3MxE4wWb ReaGA37SKINKmO/IQVgqfdbDP5JuD2kJ+Je3XKn5Bf4S7WcGczD8fMr6QC7BqhWTFUja SdTipH7v6we12z7fHAykCU+HPJHqRR2NxGWFs9QBRLRf8ElGS0D9e2nQ5reiwJdlKd5m 3cTTOF5ccAXpe2Ra2kL4ymlznmDgXg9GfCUSdoQc8MUh7py3IUZUDss4GzBGzr5XlB5C fqpg== X-Gm-Message-State: AOJu0Yy+4uo4m4WMrwcnZMKP8FYhTY8rJhEnjrG/DiOWu532G4tVWSFr jfFS71pf5GhN2NjXNAQPOJJDvOSaReertpOmEgeJbTwcTS9w2XpiKQPScffGU9Exo3AlRiZOjHD ZSO/BPPCtCw1h5Bd8Fj4x3wcT0pFrJRmjGNt4Og== X-Gm-Gg: ASbGncv3IGrZozbTv8GA/evCoZM/HB7tUIt6olefl1JkjvQwxzJ0CgGWdkJ78r4VBHz haC5NG+dZjn7MJ8vH+A0c0+C0g9ZtoR0NMNtqwu8U7mOKexXdxcflapS8Ja3IdYq8Wmc4H6E1jj 61pWqWhx7vRG1HEHXdV1y7D3Py7dyK2hce8Ys+igOhvZMpD7vcGkkF88nCZKHeDEHVVnClIcbxw MtCPA== X-Google-Smtp-Source: AGHT+IHANwUJlKPfOn0ZMzN/m0DDD4piLjqKjxCfe2bhM+i72r+eTq0gdcv2+HlI/3gXDU/kA7kvxrhpDxY8p3R3X88= X-Received: by 2002:a17:902:d505:b0:234:595d:a58e with SMTP id d9443c01a7336-24459873e4dmr242741915ad.25.1755519532410; Mon, 18 Aug 2025 05:18:52 -0700 (PDT) MIME-Version: 1.0 From: Jonathan Abdiel Gonzalez Valdebenito Date: Mon, 18 Aug 2025 14:18:40 +0200 X-Gm-Features: Ac12FXyz8HCWILdDt709DhD4mAPBuvLu47brqDBCiZrbFzou-oOOETtkvo28-vc Message-ID: Subject: Support for listing the beta versions To: pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000202d57063ca2bee6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000202d57063ca2bee6 Content-Type: text/plain; charset="UTF-8" Hello, Sometime ago I find out about this beautiful URL https://www.postgresql.org/versions.json which turns out to be really useful to get the latest available versions of PostgreSQL for automation process(building and testing mostly) but I sadly find out that the beta versions aren't listed. To show first how we use it first we parse and transform the content[1] into a compatible format that is useful for us (HCL), this is then updated[2] to make the build process easy and transparent for testing[3] in other projects. Does the site provide a way to get the active beta versions or is there a plan to publish those active beta versions? I know that most people will ask themself "why is this useful?" but testing beta versions is really useful to detect bugs and also, having that automated it's something really useful so people can focus on the bugs not on remembering to update some configuration file. Regards! [1] https://github.com/cloudnative-pg/postgres-containers/pull/269/files#diff-ff9c56df6264f225b05fd0745304138d7da5a9ac2131474d13a13d99adbe2c09R29 [2] https://github.com/cloudnative-pg/postgres-containers/blob/main/docker-bake.hcl#L35 [3] https://github.com/cloudnative-pg/postgres-trunk-containers/ --000000000000202d57063ca2bee6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

Sometime ago I find out about th= is beautiful URL=C2=A0= https://www.postgresql.org/versions.json which turns out to be really u= seful to get the latest available versions of PostgreSQL for automation pro= cess(building and testing mostly) but I sadly find out that the beta versio= ns aren't listed.

To show first how we use it = first we parse and transform the content[1] into a compatible format that i= s useful=C2=A0for us (HCL), this is then updated[2] to make the build proce= ss easy and transparent for testing[3] in other projects.

Does the site provide a way to get the active beta versions or is t= here a plan to publish those active beta versions?

I know that most people will ask themself "why is this useful?" = but testing beta versions is really useful to detect bugs and also, having = that automated it's something really useful so people can focus on the = bugs not on remembering to update some configuration file.
--000000000000202d57063ca2bee6--