Skip to content

fix: update npm publish command to handle prerelease tagging#290

Merged
AnirudhOH merged 2 commits intoqafrom
mavericks/ONCEHUB-116976
Apr 10, 2026
Merged

fix: update npm publish command to handle prerelease tagging#290
AnirudhOH merged 2 commits intoqafrom
mavericks/ONCEHUB-116976

Conversation

@khushigupta0625
Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI review requested due to automatic review settings April 10, 2026 10:56
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the npm publishing GitHub Actions workflow to publish prereleases under a non-latest dist-tag.

Changes:

  • Replaces npm run publish with an inline shell conditional that selects --tag beta for prereleases and --tag latest otherwise.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/npm-publish.yml
Comment on lines +34 to +38
if [ "${{ github.event.release.prerelease }}" = "true" ]; then
npm publish --access public --tag beta
else
npm publish --access public --tag latest
fi
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

workflow_dispatch runs won’t have github.event.release.prerelease set, so this condition will evaluate false and the workflow will always publish with the latest tag when manually triggered. If manual runs are expected, consider adding an explicit workflow_dispatch input for the desired tag (or gate the prerelease check on github.event_name == 'release') to avoid accidentally publishing a prerelease as latest.

Copilot uses AI. Check for mistakes.
@AnirudhOH AnirudhOH merged commit 1b5f77e into qa Apr 10, 2026
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.

3 participants