Skip to content

build: start the postgres base images at epoch 1 for the first produc… - #34

Merged
maqeel75 merged 1 commit into
mainfrom
spock-5.0.12
Oct 1, 2026
Merged

maqeel75 merged 1 commit into
mainfrom
spock-5.0.12

Conversation

@maqeel75

@maqeel75 maqeel75 commented Oct 1, 2026

Copy link
Copy Markdown
Member

…tion release

@coderabbitai

coderabbitai Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 69126da5-20cd-444c-8b78-06421ce07db1

📥 Commits

Reviewing files that changed from the base of the PR and between f993f1e and 1419991.

📒 Files selected for processing (1)
  • scripts/build_pgedge_images.py

Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.


📝 Walkthrough

Walkthrough

The PostgreSQL-only base image entries for versions 16.15, 17.11, and 18.6 now use epoch 1 instead of epoch 4. Their latest-for-major settings remain unchanged.

Changes

PostgreSQL Image Epochs

Layer / File(s) Summary
Update base image epochs
scripts/build_pgedge_images.py
The entries for versions 16.15, 17.11, and 18.6 change their epoch values from 4 to 1. Their latest-for-major settings remain unchanged.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 14199

The epoch updates match the first-production-release intent. No actionable merge-blocking risk is established by the supplied evidence.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: starting PostgreSQL base images at epoch 1 for the first production release.
Description check ✅ Passed The description refers to the first production release, which is related to the epoch change in the images.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
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.
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


A rabbit checks the image rows,
Three epochs shift where each one goes.
The latest flags stay as they were,
While version numbers keep their place.
Soft paws hop past the changed values,
Then tuck the build script in the hay.

Comment @coderabbitai help to get the list of available commands.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@maqeel75
maqeel75 merged commit e4e2112 into main Oct 1, 2026
93 of 94 checks passed
@maqeel75
maqeel75 deleted the spock-5.0.12 branch October 1, 2026 13:24
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