Skip to content

Conversation

cvvergara
Copy link
Member

@cvvergara cvvergara commented Jan 27, 2025

Changes proposed in this pull request:

@pgRouting/admins

Summary by CodeRabbit

  • New Features

    • No new features added in this release.
  • Bug Fixes

  • Documentation

    • Updated release notes for pgRouting version 3.7.3
    • Added links to GitHub milestones for closed issues and pull requests
  • Chores

    • Upgraded project version from 3.7.2 to 3.7.3
    • Updated version references in workflow configurations and testing scripts

@cvvergara cvvergara added this to the Release 3.7.3 milestone Jan 27, 2025
@cvvergara cvvergara requested a review from robe2 January 27, 2025 04:59
Copy link
Contributor

coderabbitai bot commented Jan 27, 2025

Walkthrough

This pull request represents a version update from 3.7.2 to 3.7.3 for the pgRouting project. The changes span multiple files across the project's configuration, workflow, documentation, and testing infrastructure. The update involves modifying version numbers in GitHub Actions workflows, CMakeLists.txt, release notes, documentation, and test result files to consistently reflect the new version number.

Changes

File Change Summary
.github/workflows/boost_version.yml Updated script version from 3.7.2 to 3.7.3
.github/workflows/update.yml Updated PostgreSQL extension version and matrix versions
CMakeLists.txt Updated project version to 3.7.3 and modified old signatures list
NEWS.md Added release notes section for version 3.7.3
doc/src/release_notes.rst Added release notes section for version 3.7.3
docqueries/version/full_version.result Updated version output to 3.7.3
docqueries/version/version.result Updated version output to 3.7.3
tools/testers/pg_prove_tests.sh Updated script version parameter to 3.7.3

Possibly related PRs

Suggested labels

tools

Suggested reviewers

  • robe2

Poem

🐰 Hop, hop, version update time!
From 3.7.2 to 3.7.3 we climb
Workflows dance, docs shine bright
pgRouting leaps with pure delight
A rabbit's version bump, so sublime! 🚀


📜 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 85b809d and f9be361.

📒 Files selected for processing (8)
  • .github/workflows/boost_version.yml (1 hunks)
  • .github/workflows/update.yml (2 hunks)
  • CMakeLists.txt (2 hunks)
  • NEWS.md (1 hunks)
  • doc/src/release_notes.rst (1 hunks)
  • docqueries/version/full_version.result (1 hunks)
  • docqueries/version/version.result (1 hunks)
  • tools/testers/pg_prove_tests.sh (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. (Beta)
  • @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.

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.

@cvvergara
Copy link
Member Author

@coderabbitai review
@coderabbitai summary

Copy link
Contributor

coderabbitai bot commented Jan 27, 2025

@cvvergara I'll review the changes for the version bump to 3.7.3.

The changes look consistent across all files:

  • Version updated from 3.7.2 to 3.7.3 in CMakeLists.txt and related files
  • Release notes updated to document the fix for build failure on Ubuntu 22 (Build Failure on Ubuntu 22 #2731)
  • Test configurations updated with the new version
  • Workflow files updated to include 3.7.2 in the list of old versions

The changes appear to be complete and correct for a version bump. I'll proceed with a detailed review.

🔗 Analysis chain
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Fetch PR details
gh pr view 2738 --json files,commits

# Get the diff of changes
git diff origin/main...HEAD

# Look for version related files
fd -t f "version|VERSION" -X cat

Length of output: 39857

✅ Actions performed

Summary regeneration triggered.

@cvvergara cvvergara merged commit 90ddfc7 into pgRouting:main Feb 6, 2025
26 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Feb 27, 2025
@cvvergara cvvergara deleted the pump-up-to-3.7.3 branch March 22, 2025 14:46
@coderabbitai coderabbitai bot mentioned this pull request Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants