ci: run checks and publish on release branches

[radu-mocanu]

Scopes both workflows to release/** in addition to main.

 # ci.yml
   push:
     branches:
       - main
+      - 'release/**'
     paths-ignore:
       - pyproject.toml
   pull_request:
     branches:
       - main
+      - 'release/**'

 # cd.yml
   push:
     branches:
       - main
+      - 'release/**'
     paths:
       - pyproject.toml

Why

Hotfix releases are cut on release/* branches, but both workflows are scoped to main only.

Checks never run. ci.yml fires only for PRs targeting main, and it is the only workflow that calls lint.yml, test.yml and commitlint.yml. The MainProtect ruleset covers refs/heads/release/* and requires lint / Lint, commit-lint / Commit Lint, SonarCloud Code Analysis and the six test / Test (3.x, uipath-{ubuntu,windows}-latest) contexts. For a PR into a release branch nothing produces them, so every one sits at Expected — Waiting for status to be reported and the PR is unmergeable without an admin bypass. That happened on #1058, which had to be force-merged despite a clean local run.

Publishing never happens. cd.yml fires only on push to main, so merging a hotfix into its release branch publishes nothing and every release needs a manual workflow_dispatch. A dispatch also runs the workflow file from the dispatched ref, so a branch cut from an older commit runs an older CI definition than main's.

Is auto-publishing from a release branch safe

The pypi environment has no deployment branch policy or protection rules, so a release ref is already permitted to publish, and release/* is covered by MainProtect, which requires a pull request — nothing lands there unreviewed. The trigger is already filtered to paths: pyproject.toml, so only a version or dependency change starts a run.

Worth noting that this repo's publish step does not pass skip-existing, so a push touching pyproject.toml without a version bump would fail at upload rather than no-op. Happy to add skip-existing: true here if you would rather it be silent.

Known limitation

This does not retroactively fix a hotfix branch cut from a commit that predates the uipath-ubuntu-latest runner rename. Such a branch produces contexts named test / Test (3.11, ubuntu-latest), which do not match what the ruleset requires, so those PRs still need a bypass or a workflow sync. This change is what stops it recurring for branches cut from here on.

[Copilot]

🟢 Approval recommended

Pull request overview

This PR updates the repository’s CI and CD GitHub Actions workflows so they trigger not only on main, but also on release/** branches. This aligns workflow execution with the project’s hotfix/release process so required status checks and publishing can run on release branches.

Changes:

• Extend .github/workflows/ci.yml triggers to run on push and pull_request events targeting release/** in addition to main.
• Extend .github/workflows/cd.yml push trigger to run on release/** (still scoped to changes in pyproject.toml) in addition to main.

File summaries

File	Description
.github/workflows/ci.yml	Adds release/** to push and pull_request branch filters so CI reusable workflows run for release-branch PRs and pushes.
.github/workflows/cd.yml	Adds release/** to the push branch filter so publishing can occur from release branches when pyproject.toml changes.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud