fix: pipeline ci

[RambokDev]

Summary by CodeRabbit

• Chores
  • Updated internal CI/CD workflow configuration.

Note: This release contains no user-facing changes. The updates are internal infrastructure modifications.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The GitHub Actions release workflow trigger was changed from pull_request to pull_request_target while retaining the closure and main branch conditions. All workflow logic, job conditions, and steps remain unchanged.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/release.yml	Updated workflow trigger from pull_request to pull_request_target with types: [closed] and branches: [main] filters intact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• dev #177: Modifies the same .github/workflows/release.yml file with changes to workflow triggers and release-publishing steps.
• fix/readme #209: Related to trigger context differences between pull_request and pull_request_target event contexts affecting job behavior.
• dev #179: Alters the same release workflow's trigger configuration, changing to tag pushes and other job modifications.

Poem

🐰 A trigger transformed, from pull to target's keep,
Where secrets stay safe in the workflow's deep,
The main branch flows on, secure and bright,
Release workflows hop through the GitHub night! 🌙✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix: pipeline ci' is vague and generic. While it mentions 'pipeline' and 'ci', it does not clearly communicate the specific change being made (switching workflow trigger from pull_request to pull_request_target).	Provide a more specific title that clearly describes the main change, such as 'fix: update release workflow trigger to pull_request_target' or 'fix: change workflow from pull_request to pull_request_target event'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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
• Commit unit tests in branch fix/pipeline-ci

---

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