enroll parseaple into buildspace

[Yan Xue (yanxue06)]

Summary by CodeRabbit

• Chores
  • Configured automated release workflow for GitHub Actions to enable continuous deployment on commits to the main branch.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow is added that automatically triggers release processes on main branch pushes, delegating execution to a reusable workflow while specifying service name, packages to release, and forwarding required secrets.

Changes

Cohort / File(s)	Summary
Release Workflow Configuration .github/workflows/release.yaml	New workflow defining automated releases triggered on main branch pushes. Delegates to a reusable TypeScript monorepo release workflow from photon-hq/buildspace, configured with service name "parseaple", two packages (bplist and typedstream), and forwarded secrets (OPENAI_API_KEY, NPM_TOKEN).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰✨ A workflow springs to life so bright,
With packages bundled, ready to flight,
Main branch pushes trigger the dance,
Release automation—no need for a glance!
Two treasures ship forth with secrets in hand! 📦🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'enroll parseaple into buildspace' directly and clearly describes the main change: adding the parseaple project to the buildspace CI/CD system via the new release workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ENG-950-Enroll-Into-BuildSpace

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[Copilot]

Pull request overview

Adds a GitHub Actions Release workflow that delegates publishing/release automation to the shared photon-hq/buildspace reusable workflow for the parseaple monorepo packages.

Changes:

• Introduces .github/workflows/release.yaml triggered on pushes to main.
• Calls the shared typescript-monorepo-release.yaml workflow with package metadata and release settings.
• Forwards NPM_TOKEN (and OPENAI_API_KEY) secrets to the reusable workflow.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yaml:
- Around line 9-23: Replace the floating ref on the reusable workflow by pinning
the `uses:
photon-hq/buildspace/.github/workflows/typescript-monorepo-release.yaml@main`
entry to a full commit SHA (e.g. change the `@main` suffix to the repository
commit SHA) so the external workflow is immutable; also audit whether
`OPENAI_API_KEY` is required by that workflow and if not remove `OPENAI_API_KEY:
${{ secrets.OPENAI_API_KEY }}` from the `secrets:` mapping while keeping
`NPM_TOKEN` (and ensure `permissions: contents: write` remains intentional
because this job publishes).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7ac6e8a0-4602-465f-8d01-a357860a970a

📥 Commits

Reviewing files that changed from the base of the PR and between e40d055 and c727711.

📒 Files selected for processing (1)

• .github/workflows/release.yaml

📜 Review details

🔇 Additional comments (1)

.github/workflows/release.yaml (1)

21-23: Verify that OPENAI_API_KEY is actually needed.

This secret is being forwarded to a reusable workflow in another repository, which expands the blast radius of the release job. If the workflow only needs npm publishing credentials, drop it; otherwise document why it is required.

🔍 Minimal change if it is unused

     secrets:
-      OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
       NPM_TOKEN: ${{ secrets.NPM_TOKEN }}