Skip to content

chore: Update release branch and latest version in workflow - #55

Merged
cbaker6 merged 4 commits into
mainfrom
cbaker6-patch-1
Nov 16, 2026
Merged

cbaker6 merged 4 commits into
mainfrom
cbaker6-patch-1

Conversation

@cbaker6

@cbaker6 cbaker6 commented Nov 16, 2026

Copy link
Copy Markdown
Member

No description provided.

Copilot AI balanced review requested due to automatic review settings November 16, 2026 22:40
@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Explain Change →

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 57 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 97142860-464b-4ae4-aacb-77a4ea70d685
Commits

Reviewing files that changed from the base of the PR and between 47c0201 and d86f74c.

Files selected for processing: 2

  • Dockerfile
  • Dockerfile.pgpool

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Release Updates
    • Release publishing now follows the 18-3.7 branch for both standard and pgpool releases.
    • The latest release designation has moved from 18-3.6 to 18-3.7, so builds from 18-3.7 receive the latest-release label.
    • Existing release triggers for the main and 15-3.3 branches remain unchanged.

Both release workflows now trigger on pushes to 18-3.7 and set LATEST to 18-3.7.

Changes: Release workflows

Layer / File(s) Summary
Update release branch target
.github/workflows/release.yml, .github/workflows/release-pgpool.yml
Both workflows replace 18-3.6 with 18-3.7 in their push triggers and LATEST values. The main and 15-3.3 push branches in the pgpool workflow remain configured.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · previous review 47c02

This updates both release workflows to treat 18-3.7 as the latest release branch. No concrete problem was found in the change. Create the 18-3.7 branch from main, or from a commit that includes these workflow updates, so pushes to it trigger the workflows.

Pre-merge checks: Passed 3 · Inconclusive 1

Failed Failed checks: 1 inconclusive

Check name Status Explanation Resolution
Description check Inconclusive The author gave no description. The check is lenient, but this case has no description text to judge. The PR objectives and the file summaries show the change is a two-line version bump in the release… Add a short description that names the new release branch (18-3.7), notes that LATEST moves from 18-3.6 to 18-3.7, and states why the bump is needed.
Passed Passed checks: 3 passed

Check name Status Explanation
Title check Passed The title names the main change: the release workflow now targets the 18-3.7 branch and sets LATEST to 18-3.7. It is a short, specific chore title that matches both changed workflow files.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The author gave no description. The check is lenient, but this case has no description text to judge. The PR objectives and the file summaries show the change is a two-line version bump in the release workflows, so the missing description is not a relevance problem for this check.

Resolution

Add a short description that names the new release branch (18-3.7), notes that LATEST moves from 18-3.6 to 18-3.7, and states why the bump is needed.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Two workflows point to a new branch,
18-3.7 joins the release march.
LATEST now names the same,
Both triggers follow suit.
Plus Ultra, releases set their route!

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 3718d7df-1eda-4652-a67b-858a268fd522
Commits

Reviewing files that changed from the base of the PR and between 0157615 and 47c0201.

Files selected for processing: 2

  • .github/workflows/release-pgpool.yml
  • .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the release workflow update to 18-3.7.

No open issues 🎉

What changed in this PR

This PR advances the release workflow from 18-3.6 to 18-3.7, aligning its push trigger and latest-version setting.

Changes:

  • Replace 18-3.6 with 18-3.7 in the push-trigger branches, retaining main and 15-3.3.
  • Update LATEST to 18-3.7.
File Description
.github/​workflows/​release.yml Update the release branch trigger and latest-version setting to 18-3.7.

Review effort: Balanced

@cbaker6
cbaker6 merged commit 0d4023a into main Nov 16, 2026
5 checks passed
@cbaker6
cbaker6 deleted the cbaker6-patch-1 branch November 16, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants