Skip to content

fix: use ubuntu-latest runner for pull_request job - #14

Merged
ivancalvo-dbxs merged 1 commit into
mainfrom
fix/github-actions
Aug 26, 2026
Merged

fix: use ubuntu-latest runner for pull_request job#14
ivancalvo-dbxs merged 1 commit into
mainfrom
fix/github-actions

Conversation

@ivancalvo-dbxs

Copy link
Copy Markdown
Collaborator

Summary

  • Swap runs-on from databricks-solutions-protected-runner-group to ubuntu-latest on the pull_request job in test-deploy.yml
  • Drop JFrog OIDC token step and npm registry config - the PR job is a secretless build that only needs public npm
  • Remove id-token: write permission (no longer needed without JFrog)

Context

Per confirmed policy (Slack thread: https://databricks.slack.com/archives/C0AQGH6KJS1/p1787067996946379), on public repos the pull_request path must run on GitHub-hosted runners, not the internal protected runner group. Untrusted fork-PR code should not execute on VNet-attached internal runners.

deploy.yml is unchanged - it only triggers on push to main, so it stays on the protected runner.

Test plan

  • CI passes on this PR with ubuntu-latest runner

Public repos must run the pull_request path on GitHub-hosted runners,
not the internal protected runner group (confirmed policy). The PR job
is a secretless build so it needs neither the hardened group nor JFrog.
@ivancalvo-dbxs
ivancalvo-dbxs merged commit ec8916f into main Aug 26, 2026
1 check passed
@ivancalvo-dbxs
ivancalvo-dbxs deleted the fix/github-actions branch September 1, 2026 19:42
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.

1 participant