Skip to content

refactor(ci): enhance native package version check with retry logic and error handling#97

Open
ashikvarma11 wants to merge 3 commits intodoctypedev:mainfrom
ashikvarma11:issue-70
Open

refactor(ci): enhance native package version check with retry logic and error handling#97
ashikvarma11 wants to merge 3 commits intodoctypedev:mainfrom
ashikvarma11:issue-70

Conversation

@ashikvarma11
Copy link
Copy Markdown
Contributor

Description

Improve robustness of the native package publishing workflow by adding:

  • Error handling for version extraction from package.json with early exit on failure
  • Retry logic (3 attempts with 2-second delays) for npm registry queries to handle transient network issues
  • 10-second timeout protection on npm view commands to prevent workflow hangs
  • Enhanced logging with detailed status messages for better debuggability
  • Robust version comparison using proper bash conditionals to handle edge cases
  • Clear decision flow distinguishing between already-published, not-yet-published, and version-mismatch scenarios

These changes maintain backward compatibility while significantly improving reliability and resilience of the release workflow, especially in scenarios with temporary registry connectivity issues.

Fixes: #70

@vercel
Copy link
Copy Markdown

vercel bot commented Dec 4, 2025

@ashikvarma1 is attempting to deploy a commit to the alessiopelliccione's projects Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link
Copy Markdown

vercel bot commented Dec 4, 2025

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/alessiopellicciones-projects?upgradeToPro=build-rate-limit

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.

Improve publish.yml by refining version check to handle edge cases more robustly

2 participants