Testing Postgres 17

[cvvergara]

Changes proposed in this pull request:

• Test with postgreSQL 17

@pgRouting/admins

Summary by CodeRabbit

• Chores
  • Enhanced automated testing by expanding compatibility with the latest database version, ensuring improved stability and reliability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the GitHub Actions workflow by modifying the matrix configuration in the CI pipeline. Specifically, it expands the list of PostgreSQL versions to include version 17 alongside the previously supported versions 13, 14, 15, and 16. This alteration affects the test and build jobs in the CI/CD pipeline.

Changes

File	Change Summary
.github/workflows/ubuntu.yml	Updated the matrix configuration to add PostgreSQL version 17 to the list of tested versions.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHubActions as GH Actions
    participant JobRunner as Job Runner
    participant PostgresEnv as PostgreSQL Environment

    Developer->>GH Actions: Push commit
    GH Actions->>JobRunner: Trigger workflow with matrix (13, 14, 15, 16, 17)
    loop For each PostgreSQL version
        JobRunner->>PostgresEnv: Setup PostgreSQL (current version)
        PostgresEnv-->>JobRunner: Return environment ready
        JobRunner->>PostgresEnv: Run tests/build
        PostgresEnv-->>JobRunner: Return test/build result
    end
    JobRunner-->>GH Actions: Aggregate results
    GH Actions-->>Developer: Report CI/CD status

Loading

Poem

I am a rabbit with a joyful heart,
Hopping through code changes, a brand-new start.
PostgreSQL versions now bloom with zest,
Our CI pipeline put to the test.
With every poke and hop, bugs depart!
🐇🌸

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e252a6 and 20ab78c.

📒 Files selected for processing (1)

• .github/workflows/ubuntu.yml (1 hunks)

---

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.