mirror of
https://github.com/cline/cline.git
synced 2026-08-30 17:20:20 +08:00
Saoud Rizwan
eeaed357ef
The branch dispatch input was a free-form string with no validation. Both jobs checked it out and ran full npm lifecycle scripts from it: the publish job next to VSCE_PAT/OVSX_PAT (and npm run publish:marketplace executes a script from that same ref with the PATs in env), and the test job with NO environment approval at all while inheriting the workflow-level contents/packages/checks/pull-requests write grants. A dispatch pointing at e.g. refs/pull/N/head would run outside-contributor code with the marketplace keys behind one approval, or with a repo-write token behind none. Remove the input and hardcode the protected legacy-extension branch, drop the workflow-level permissions to contents: read, and elevate only the publish job to contents: write (tag push + GitHub release). The branch input's default was legacy-extension, so normal publishes are unchanged. publish-extension skill dispatch command updated to match.