ci(repo): improve verdaccio proxy verification with retries#7782
ci(repo): improve verdaccio proxy verification with retries#7782jacekradko merged 2 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
📝 WalkthroughWalkthroughThe GitHub Actions workflow file for Verdaccio proxy verification has been updated to test multiple packages instead of a single package. The change introduces a list of three test packages (semver, browserslist, update-browserslist-db) and implements retry logic with configurable maximum retries and delay between attempts. The verification now iterates through each package, attempting to fetch the specified version up to the configured number of times before ultimately failing or succeeding based on all packages passing verification. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Summary
update-browserslist-dbwhich caused recent CI failuresContext
Recent CI failures showed integration tests timing out because Verdaccio's npm proxy wasn't working properly:
The previous implementation only logged a warning if proxy verification failed, allowing tests to proceed and fail later with cryptic timeout errors.
Test plan
Summary by CodeRabbit