upgrade to postgres17rc1

[ImreSamu]

medium changes.

steps:

• git mv 17beta3-master 17rc1-master
• git mv 17beta3-3.5.0alpha2 17rc1-3.5.0alpha2
• run: ./update.sh
• .github/workflows/main.yml : replace 17beta3 to 17rc1
• README.md : updated test image info

( fixing #389 )

Extra:

• Added experimental codderabit config

Expected next week:

• PostGIS 3.4.3 debian upgrade
• PostGIS 3.5.0beta1

Status: All build OK ; ready to review

[coderabbitai]

Walkthrough

Walkthrough

The changes in this pull request involve updates to the PostgreSQL version across various configuration files, transitioning from 17beta3 to 17rc1. This includes modifications in GitHub Actions workflows, Dockerfiles for different builds, and the README documentation. Additionally, specific Git commit hashes for dependencies in the Dockerfiles have been updated to reflect new versions, ensuring compatibility with the latest library features and fixes.

Changes

File Path	Change Summary
.github/workflows/main.yml	Updated PostgreSQL version from 17beta3 to 17rc1 (default and alpine variants).
15-master/Dockerfile, 16-master/Dockerfile	Updated Git commit hashes for dependencies: CGAL, SFCGAL, PROJ, GEOS, GDAL, and POSTGIS.
17rc1-3.5.0alpha2/alpine/Dockerfile	Changed base image from postgres:17beta3-alpine3.20 to postgres:17rc1-alpine3.20.
17rc1-master/Dockerfile	Changed base image from postgres:17beta3-bullseye to postgres:17rc1-bullseye and updated Git hashes.
README.md	Updated version header from "2024-08-20" to "2024-09-14" and replaced references from "17beta3" to "17rc1".

Possibly related PRs

• Upgrade to 17beta3 #388: The changes in this PR involve updating the PostgreSQL version in the GitHub Actions workflow from 17beta2 to 17beta3, which is directly related to the main PR's update from 17beta3 to 17rc1, indicating a progression in the PostgreSQL versioning.

🐇 In a garden where changes bloom,
PostgreSQL's new version finds room.
From beta to candidate, a leap so bright,
With dependencies updated, all feels right.
Hop along, dear friends, let’s celebrate,
For progress in code is truly first-rate! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[phillipross]

This looks great, thanks! I'm going to go ahead and merge w/ a rebase+commit instead of a squash commit so that the code rabbit change stays on its own commit. It may be helpful to have that commit isolated for reference down the road 😁

Thanks!