docs: update release process for publish pipeline

[tsivaprasad]

Summary

This PR updates the release process documentation to describe the package publishing pipeline introduced.

Changes

• docs/development/development.md — updated the "Running the
  Release Process" section to describe that the CircleCI release job
  now creates a draft release, builds and signs RPM/DEB packages,
  attaches them, and un-drafts the release. Documents the GitHub
  Actions publish.yml workflow that pushes packages to the pgEdge
  dnf/apt repos and sends a Slack notification.

Testing

• Reviewed against the implementation in PR Add dnf/apt package publishing pipeline #425.

Checklist

• Documentation updated (docs/development/development.md)

PLAT-683

[coderabbitai]

Warning

Review limit reached

@tsivaprasad, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2c1e8fd7-b724-48fd-9643-3363635752a0

📥 Commits

Reviewing files that changed from the base of the PR and between 6ad7bd2 and 15e15f2.

📒 Files selected for processing (1)

• docs/development/development.md

📝 Walkthrough

Walkthrough

Changes

Release Documentation

Layer / File(s)	Summary
Draft release publication flow docs/development/development.md	Documents draft release creation, artifact uploads, signed package attachments, publish.yml distribution steps, pre-release routing to staging, and GA routing to the staging channel.

Poem

I’m a bunny with binaries tucked in my pack,
SBOMs and checksums all neatly stacked.
Drafts hop to publish, packages fly,
RPMs and DEBs reach repositories nearby.
S3 keeps backups safe and sound,
While Slack cheers when releases are found.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the documentation update for the release publishing pipeline.
Description check	✅ Passed	The description follows the template well with Summary, Changes, Testing, and Checklist sections and stays on-topic.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch PLAT-683-review-adjust-package-publishing-workflow-for-release

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codacy-production]

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

[susan-pgedge]

Looks good to me @tsivaprasad !