Skip to content

ci: deploy manually to canary env from main #2627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
serhalp merged 5 commits into from
Apr 26, 2026
Merged

ci: deploy manually to canary env from main #2627

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6386685
ci: deploy manually to canary env from main
serhalp Apr 25, 2026
aa72bd9
Potential fix for pull request finding 'CodeQL / Workflow does not co…
serhalp Apr 25, 2026
0f68cad
ci: add missing env vars, configure concurrency
serhalp Apr 25, 2026
31cd899
ci: remove unnecessary default fetch-depth opt
serhalp Apr 25, 2026
ff60b88
ci: use vp instead of npmx
serhalp Apr 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .github/workflows/deploy-canary.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
on:
push:
branches: [main]

jobs:
deploy-canary:
if: github.repository == 'npmx-dev/npmx.dev'
name: 🚀 Deploy to canary (main.npmx.dev)
runs-on: ubuntu-24.04-arm
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
fetch-depth: 0
Comment thread
serhalp marked this conversation as resolved.
Outdated
- run: npx vercel deploy --target=canary --token="$VERCEL_TOKEN"
Comment thread
serhalp marked this conversation as resolved.
Outdated
env:
VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment thread
github-advanced-security[bot] marked this conversation as resolved.
Fixed
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Outdated
Loading