fix: revert spock 5.0.7 image change to unpublish

[mmols]

Summary

Reverts PR #19 (spock 5.0.7 update) to move the mutable image tags back to spock 5.0.6 variants. Restores the script's spock_version to 5.0.6 / epoch=2 across pg16/17/18 and renames the packagelists back to pg*-spock5.0.6-*.txt.

The 5.0.6 immutable tags (*-spock5.0.6-{minimal,standard}-2) still exist in the registry, so the build-images workflow will skip the build step and only re-point the mutable tags (*-spock5*-*, *-spock5.0.6-*) at the existing 5.0.6 manifests via docker buildx imagetools create.

5.0.7 immutable tags will be deleted manually in the GHCR UI after merge.

Test plan

Run the build-images workflow against the internal repo before merging:

• Dry run on internal: Actions → build-images → Run workflow on this branch with:
  • pgedge_image_repo: ghcr.io/pgedge/pgedge-postgres-internal (default)
  • pgedge_image_dry_run: true
  • pgedge_image_republish: false
  • Confirm the log shows <tag> is already published for each *-spock5.0.6-*-2 build tag and adding new tag ... to existing manifest for each mutable tag — no building and pushing images lines.
• Live run on internal: same inputs, pgedge_image_dry_run: false. Verify on ghcr.io/pgedge/pgedge-postgres-internal that 17-spock5-standard, 17.9-spock5-standard, 17.9-spock5.0.6-standard (and the pg16/pg18 equivalents, both flavors) resolve to the 5.0.6 manifest digest.
• After merge to main, run the same workflow against ghcr.io/pgedge/pgedge-postgres (production repo) with dry_run: true first, then live.
• Manually delete *-spock5.0.7-* versions from the production package in the GHCR UI.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 174ba665-1122-4222-8635-ea288b7332c8

📥 Commits

Reviewing files that changed from the base of the PR and between d19cdb3 and e96b668.

📒 Files selected for processing (13)

• packagelists/amd64/pg16.13-spock5.0.6-minimal.txt
• packagelists/amd64/pg16.13-spock5.0.6-standard.txt
• packagelists/amd64/pg17.9-spock5.0.6-minimal.txt
• packagelists/amd64/pg17.9-spock5.0.6-standard.txt
• packagelists/amd64/pg18.3-spock5.0.6-minimal.txt
• packagelists/amd64/pg18.3-spock5.0.6-standard.txt
• packagelists/arm64/pg16.13-spock5.0.6-minimal.txt
• packagelists/arm64/pg16.13-spock5.0.6-standard.txt
• packagelists/arm64/pg17.9-spock5.0.6-minimal.txt
• packagelists/arm64/pg17.9-spock5.0.6-standard.txt
• packagelists/arm64/pg18.3-spock5.0.6-minimal.txt
• packagelists/arm64/pg18.3-spock5.0.6-standard.txt
• scripts/build_pgedge_images.py

---

📝 Walkthrough

Walkthrough

Spock package version is downgraded from 5.0.7 to 5.0.6 across PostgreSQL 16, 17, and 18 build targets. The build matrix is updated with Spock 5.0.6 and epoch 2, followed by corresponding package manifest updates for both amd64 and arm64 architectures in minimal and standard variants.

Changes

Spock 5.0.6 Version Downgrade

Layer / File(s)	Summary
Build matrix configuration scripts/build_pgedge_images.py	The all_images build matrix entries for PostgreSQL 16.x, 17.x, and 18.x are updated to specify Spock version 5.0.6 with epoch 2 (replacing 5.0.7 with epoch 1).
AMD64 package manifests packagelists/amd64/pg16.13-spock5.0.6-minimal.txt, packagelists/amd64/pg16.13-spock5.0.6-standard.txt, packagelists/amd64/pg17.9-spock5.0.6-minimal.txt, packagelists/amd64/pg17.9-spock5.0.6-standard.txt, packagelists/amd64/pg18.3-spock5.0.6-minimal.txt, packagelists/amd64/pg18.3-spock5.0.6-standard.txt	All six amd64 package list files are updated to reference pgedge-spock50 version 5.0.6-1.el9 instead of 5.0.7-1.el9 across PostgreSQL 16, 17, and 18 with minimal and standard configurations.
ARM64 package manifests packagelists/arm64/pg16.13-spock5.0.6-minimal.txt, packagelists/arm64/pg16.13-spock5.0.6-standard.txt, packagelists/arm64/pg17.9-spock5.0.6-minimal.txt, packagelists/arm64/pg17.9-spock5.0.6-standard.txt, packagelists/arm64/pg18.3-spock5.0.6-minimal.txt, packagelists/arm64/pg18.3-spock5.0.6-standard.txt	All six arm64 package list files are updated to reference pgedge-spock50 version 5.0.6-1.el9 instead of 5.0.7-1.el9 across PostgreSQL 16, 17, and 18 with minimal and standard configurations.

Poem

🐰 A downgrade hops through versions with care,
Spock 5.0.6 spreads everywhere,
From amd64 to arm64 aligned,
PostgreSQL 16 through 18 designed,
Epoch bumped up, package lists refined! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: reverting the spock 5.0.7 update back to 5.0.6 to unpublish the newer version, which is accurate to the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining the revert from spock 5.0.7 to 5.0.6 across package lists and build scripts with comprehensive context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch revert-spock-5.0.7

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
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.}