Bumps PG minor update server and spock versions.#20
Conversation
📝 WalkthroughWalkthroughBuild configuration and package list manifests updated: Postgres patch versions bumped for majors 16/17/18, Spock upgraded to 5.0.8, epoch changed in the build script, and AMD64/ARM64 minimal/standard package lists populated or updated to match. ChangesVersion Bump Across Build Configuration and Package Manifests
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Comment |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
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.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/build_pgedge_images.py`:
- Line 169: The global matrix currently hardcodes
package_release_channel="staging" (seen where package_release_channel is set in
scripts/build_pgedge_images.py), causing every build to publish to staging;
change this to read from configuration or an environment variable with a safe
default (e.g., os.getenv("PACKAGE_RELEASE_CHANNEL", "staging") or a Config class
default) and replace the three hardcoded occurrences (the
package_release_channel assignments at the three locations) to use that
configurable value so callers can override the channel without editing code.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: e0fb2f39-ffa0-4a65-bdec-260095abd6af
📒 Files selected for processing (19)
packagelists/amd64/pg16.13-spock5.0.7-minimal.txtpackagelists/amd64/pg16.14-spock5.0.8-minimal.txtpackagelists/amd64/pg16.14-spock5.0.8-standard.txtpackagelists/amd64/pg17.10-spock5.0.8-minimal.txtpackagelists/amd64/pg17.10-spock5.0.8-standard.txtpackagelists/amd64/pg17.9-spock5.0.7-minimal.txtpackagelists/amd64/pg18.3-spock5.0.7-minimal.txtpackagelists/amd64/pg18.4-spock5.0.8-minimal.txtpackagelists/amd64/pg18.4-spock5.0.8-standard.txtpackagelists/arm64/pg16.13-spock5.0.7-minimal.txtpackagelists/arm64/pg16.14-spock5.0.8-minimal.txtpackagelists/arm64/pg16.14-spock5.0.8-standard.txtpackagelists/arm64/pg17.10-spock5.0.8-minimal.txtpackagelists/arm64/pg17.10-spock5.0.8-standard.txtpackagelists/arm64/pg17.9-spock5.0.7-minimal.txtpackagelists/arm64/pg18.3-spock5.0.7-minimal.txtpackagelists/arm64/pg18.4-spock5.0.8-minimal.txtpackagelists/arm64/pg18.4-spock5.0.8-standard.txtscripts/build_pgedge_images.py
💤 Files with no reviewable changes (6)
- packagelists/amd64/pg16.13-spock5.0.7-minimal.txt
- packagelists/arm64/pg17.9-spock5.0.7-minimal.txt
- packagelists/amd64/pg18.3-spock5.0.7-minimal.txt
- packagelists/arm64/pg18.3-spock5.0.7-minimal.txt
- packagelists/arm64/pg16.13-spock5.0.7-minimal.txt
- packagelists/amd64/pg17.9-spock5.0.7-minimal.txt
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/build_pgedge_images.py`:
- Line 166: The PR changes immutable image tags by decrementing epoch from 2 to
1 (the `epoch` value set to 1 in the image definitions), which can break version
precedence and automation; update the code by either restoring the previous
epoch or adding an explicit justification: add a short inline comment next to
each `epoch` assignment (the `epoch` variable in the image tag definitions)
explaining why you lowered it (e.g., policy change, rebuild semantics, or
coordinated versioning plan), and also add a one-line entry to the repository
changelog or the script header documenting the global rationale for the epoch
change so consumers and automation understand the new ordering. Ensure the
comment references the same `epoch` assignments so reviewers can verify
consistency across all image sets.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 2b0fd08d-5834-4310-b2b7-4ebb619f787c
📒 Files selected for processing (1)
scripts/build_pgedge_images.py
PG minor plus spock version updates