Skip to content

chore: [SDK-4532] remove unused Asana, Claude, and Unity activation workflows#868

Merged
fadi-george merged 3 commits into
mainfrom
fadi/sdk-4532
May 14, 2026
Merged

chore: [SDK-4532] remove unused Asana, Claude, and Unity activation workflows#868
fadi-george merged 3 commits into
mainfrom
fadi/sdk-4532

Conversation

@fadi-george
Copy link
Copy Markdown
Collaborator

@fadi-george fadi-george commented May 14, 2026

Description

One Line Summary

Removes unused Asana sync, Claude, and Unity activation GitHub workflows.

Details

Motivation

These workflows are no longer in use in this repo. The Asana sync workflows were also flagged in SDK-4532 for a CI hardening concern, so dropping them rather than maintaining them. activation.yml generates a Unity license activation file but nothing else in CI consumes a Unity license (ci.yml runs csharpier, cd.yml publishes npm packages).

Scope

  • Removes 6 workflow files under .github/workflows/:
    • asana-add-comment.yml
    • asana-create-task.yml
    • asana-update-issue.yml
    • claude.yml
    • claude-code-review.yml
    • activation.yml
  • Also removes .cursor/rules/pr-conventions.mdc (folded into root rules already).
  • No source code, build, test, or release behavior changes.

Testing

Manual testing

N/A, workflow file removals only. Existing ci.yml (csharpier) and cd.yml (npm publish) are untouched.

Affected code checklist

  • Notifications
  • Outcomes
  • Sessions
  • In-App Messaging
  • REST API requests
  • Public API changes

Checklist

Overview

  • I have filled out all REQUIRED sections above
  • PR does one thing
  • Any Public API changes are explained in the PR details and conform to existing APIs

Testing

  • I have included test coverage for these changes, or explained why they are not needed
  • All automated tests pass, or I explained why that is not possible
  • I have personally tested this on my device, or explained why that is not possible

Final pass

  • Code is as readable as possible.
  • I have reviewed this PR myself, ensuring it meets each checklist item

fadi-george and others added 3 commits May 14, 2026 15:01
Removes the Asana sync workflows (asana-add-comment, asana-create-task,
asana-update-issue) and the Claude workflows (claude, claude-code-review).

The Asana update workflow contained a script-injection vulnerability via
issue title interpolated into a shell `run:` block (SDK-4532). Rather
than patch it, dropping these workflows since they are no longer needed.

Co-authored-by: Cursor <cursoragent@cursor.com>
The activation.yml workflow generates a Unity license activation request
file (.alf), but no other workflow in this repo uses a Unity license
(ci.yml only runs csharpier; cd.yml only publishes npm packages). It is
also a manual workflow_dispatch and the underlying actions/upload-artifact@v2
is deprecated.

Co-authored-by: Cursor <cursoragent@cursor.com>
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — pure deletion of unused workflow files; removing the vulnerable asana-update-issue.yml is a clean fix for SDK-4532, and the other removals (asana-, claude, activation.yml, .cursor/rules/pr-conventions.mdc) have no runtime impact on ci.yml/cd.yml.

Extended reasoning...

Overview

This PR is a pure-deletion change touching 6 GitHub workflow files under .github/workflows/ (asana-add-comment.yml, asana-create-task.yml, asana-update-issue.yml, claude.yml, claude-code-review.yml, activation.yml) and one Cursor rule file (.cursor/rules/pr-conventions.mdc). No source code, build configuration, tests, or release behavior is modified. The remaining ci.yml (csharpier) and cd.yml (npm publish) workflows are untouched.

Security risks

Net-positive for security. The primary motivation is SDK-4532: asana-update-issue.yml interpolated user-controllable GitHub event fields (github.event.issue.title, github.event.label.name, github.event.milestone.title, github.event.changes.title.from, etc.) directly into shell run: blocks via ${{ }}, which is a well-known script-injection vector. Removing the file eliminates the vulnerability entirely rather than patching it. No new attack surface is introduced. Removing the Claude workflows reduces the number of pipelines that hold elevated tokens.

Level of scrutiny

Low. This is a mechanical deletion of unused CI/tooling files with a clearly stated rationale. There is no logic to reason about, no API surface change, and no risk to consumers of the SDK. The only risk would be that a removed workflow is still relied upon — but the PR description explicitly confirms these are not used, and a quick sanity check of the changed-files set shows no inbound references could survive (each workflow is self-contained and triggered by GitHub events, not invoked by other workflows).

Other factors

The PR is small, self-contained, and well-described with a linked Linear ticket. No bugs were flagged by the bug hunting system. The cursor rule deletion is noted as already folded into root rules. Overall this is exactly the kind of low-risk security-hardening cleanup that is safe to shadow-approve.

Copy link
Copy Markdown

@nan-li nan-li left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it!

@fadi-george fadi-george merged commit c1b60e4 into main May 14, 2026
5 checks passed
@fadi-george fadi-george deleted the fadi/sdk-4532 branch May 14, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants