Skip to content

[Fix] Increment prerelease from npm publish tag - #25

Merged
jsaarimaa merged 1 commit into
devfrom
fix/deploy-script-fix
Sep 18, 2026
Merged

jsaarimaa merged 1 commit into
devfrom
fix/deploy-script-fix

Conversation

@jsaarimaa

@jsaarimaa jsaarimaa commented Sep 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Fix prerelease publishing for development and test environments.

The version helper previously looked up npm dist-tags using prerelease identifiers (d/t), while packages are published under dev/test. This caused the helper to repeatedly generate versions such as 0.2.3-d.0.

The workflow now passes the actual npm tag to the helper, allowing it to detect the existing prerelease and increment it to 0.2.3-d.1.

Validation

Verified prerelease increment from 0.2.3-d.0 to 0.2.3-d.1
1,144 tests passed
Lint passed
Production build passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

No blocking issues were identified, and validation passed.

Pull request overview

Fixes prerelease version increments by using the actual npm dist-tag (dev/test) when locating existing versions.

Changes:

  • Passes the npm tag to the version helper.
  • Uses NPM_TAG for prerelease lookup and incrementing.
  • Improves missing-input validation.
File summaries
File Description
.github/workflows/cd-publish.yml Passes the npm tag to the helper.
.github/scripts/version-helper.js Uses the npm tag to resolve prerelease versions.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@jsaarimaa
jsaarimaa merged commit fccaacb into dev Sep 18, 2026
6 checks passed
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