Deploy on push to main via GitHub OIDC instead of VOID_TOKEN

[fengmk2]

Bumps void to 0.10.2 and switches the push-to-main deploy workflow to the new GitHub OIDC flow: void deploy exchanges a short-lived OIDC token for a project-scoped deploy token, so the workflow no longer reads the long-lived VOID_TOKEN secret.

• deploy.yml renamed to void-deploy.yml (the platform only honors the OIDC exchange from that exact workflow path) with permissions: id-token: write.
• staging.yml (PR deploys) keeps VOID_TOKEN: the platform rejects the OIDC exchange for pull_request events, since PR runs execute untrusted code.
• This PR's own Staging check exercises void deploy 0.10.2 against the staging project through the existing token path.

Do not merge yet: both projects must first be connected with void github connect <project> --repo voidzero-dev/pkg-pr-registry-bridge --branch main --executor github_actions, otherwise every push-to-main deploy fails the OIDC exchange with a 401. Connecting is currently blocked on a github_identity_conflict (the fengmk2 GitHub identity is linked to another Void account).

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	void@​0.10.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm better-sqlite3 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/void@0.10.2 → npm/better-sqlite3@12.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/better-sqlite3@12.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm drizzle-orm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/void@0.10.2 → npm/drizzle-orm@0.45.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/drizzle-orm@0.45.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report