Skip to content

Add in-repo release workflow and spock50 RPM/DEB packaging - #549

Merged
maqeel75 merged 2 commits into
v5_STABLEfrom
release-workflow-v5
Jul 29, 2026
Merged

Add in-repo release workflow and spock50 RPM/DEB packaging#549
maqeel75 merged 2 commits into
v5_STABLEfrom
release-workflow-v5

Conversation

@maqeel75

Copy link
Copy Markdown
Member

Summary

Adds an in-repo release pipeline for the v5 series, so Spock's RPMs and DEBs are
built from this repo on a tag push instead of out of pgedge-enterprise-packages.
Packaging files are taken from that repo's spock50/ component; the workflow
follows the pgedge-postgres-mcp / pgedge-rag-server shape.

.github/workflows/release.yml — 7 jobs:
detect-matrix → determine-repo-type → package-rpm/package-deb → push-dnf/push-apt → publish-manifest
across almalinux 9/10 and jammy/noble/resolute/bullseye/bookworm/trixie, amd64 + arm64.

Notable choices

  • Per-PG fan-out. PER_PG_VERSION=true, but this repo has no postgresql-N/
    dirs, so the PG list can't be auto-discovered — passed explicitly, default
    16,17,18, overridable per run. Artifact names carry the PG major so the three
    PG cells of one (os, arch) don't collide.
  • COMPONENT_NAME=spock50, not the repo name, so v5 and v6 never share an S3
    backup path or _pending/ manifest key.
  • Source from the checkout, not a clone: each cell git archives into
    release-artifacts/, which the build scripts prefer over cloning the tag.
    Packages are the exact commit under test, and simulate_tag branch runs work.
  • Guards: tag filter v5.* plus an assert that include/spock.h
    SPOCK_VERSION equals the tag version and is 5.x.
  • DEB pre-release ordering fixed (spock50 lacked it): 5.0.11~rc1-1.noble
    now sorts below 5.0.11-1.noble.
  • Dropped debian/patches/pkglibdir.patch targets a
    spock_create_subscriber recipe that no longer exists and does not apply.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bfd2d794-e51b-4cd7-9f00-06bc13f5c3d1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-workflow-v5

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

@codacy-production

codacy-production Bot commented Jul 28, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

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 requested a review from mason-sharp July 28, 2026 12:25
@danolivo
danolivo self-requested a review July 29, 2026 11:22

@danolivo danolivo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The same as for PR#550. Basically, looks good

@maqeel75
maqeel75 merged commit e1ac496 into v5_STABLE Jul 29, 2026
59 checks passed
@maqeel75
maqeel75 deleted the release-workflow-v5 branch July 29, 2026 12:02
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