feat: fix release pipeline

[sankhavaramsaitulasiram]

Description

Types of changes

What types of changes does your code introduce?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Further comments (optional)

Summary by CodeRabbit

• Chores
  • Updated the release workflow's version extraction to a more robust JSON parsing approach. This standardizes and improves reliability of version retrieval across frontend, admin frontend, and backend services, reducing release failures and aligning behavior across projects.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The .github/workflows/release.yml workflow is changed to use jq to parse the version field from package.json files instead of using bun/Node.js require-based commands for the frontend, admin_frontend, and backend version retrieval steps.

Changes

Cohort / File(s)	Change Summary
Release Workflow Version Extraction .github/workflows/release.yml	Replaces bun/Node.js require-based version extraction with jq-based parsing of the version field from package.json for frontend, admin_frontend, and backend steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Single workflow file, consistent pattern changes across three steps.
• Review focus: confirm jq is available in runner environment, verify correct file paths and quoting, and validate no other workflow logic was altered.

Possibly related PRs

• feat: migrate to bun in github workflows #231 — Modified the same .github/workflows/release.yml version-extraction steps (different approach involving bun/Node), indicating a direct relation to extraction logic changes.

Suggested reviewers

• vignesha22

Poem

🐰 I nudge the workflow, soft and sly,

I swap the tools that parse the sky.
jq hums a tune, versions align—
A hop, a tweak, the release feels fine. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is entirely unfilled—it contains only the template placeholders with dashes and no checked checkboxes, providing no actual information about the changes, their purpose, or the specific problem being addressed.	Fill in the Description section with details about why the release pipeline needed fixing, specify the type of change (likely 'Build related changes'), and explain the impact of replacing the version extraction method.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: fix release pipeline' is partially related to the changeset—it correctly identifies a release pipeline fix, but lacks specificity about the actual technical change (replacing Node.js-based version extraction with shell pipeline commands).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 475a3c4 and deb4037.

📒 Files selected for processing (1)

• .github/workflows/release.yml (3 hunks)

---

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 and usage tips.}

[cloudflare-workers-and-pages]

Deploying arka with    Cloudflare Pages

Latest commit:	475a3c4
Status:	✅  Deploy successful!
Preview URL:	https://3e459531.arka-3qg.pages.dev
Branch Preview URL:	https://feat-fix-release-pipeline.arka-3qg.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/release.yml (1)

18-21: Remove unused bun setup steps.

The workflow still sets up bun (expensive in CI time), but the modified version extraction steps no longer use it. If bun is not needed elsewhere in the workflow, remove these setup steps to improve pipeline efficiency.

Apply this diff to all three job sections:

- - name: Setup Bun
-   uses: oven-sh/setup-bun@v2
-   with:
-     bun-version: 1.0.1

Also applies to: 50-53, 82-85

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fe41927 and 475a3c4.

📒 Files selected for processing (1)

• .github/workflows/release.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Cloudflare Pages