Skip to content

chore(js): bump package to 0.1.1 for npm release - #44

Merged
mahimairaja merged 1 commit into
mainfrom
release/js-0.1.1
Jun 30, 2026
Merged

chore(js): bump package to 0.1.1 for npm release#44
mahimairaja merged 1 commit into
mainfrom
release/js-0.1.1

Conversation

@mahimairaja

@mahimairaja mahimairaja commented Jun 30, 2026

Copy link
Copy Markdown
Member

Bumps the JS package (packages/js) from 0.1.0 to 0.1.1.

Why

envoic@0.1.0 was published then unpublished on npm back in February, and npm permanently reserves unpublished version numbers. The v0.1.0 release therefore failed with:

Cannot publish over previously published version "0.1.0".

0.1.0 can never go to npm, so the JS package needs a fresh version to ship. PyPI already has 0.1.0; moving both to 0.1.1 realigns them.

Scope

  • Only packages/js/package.json + package-lock.json (root envoic version). The yocto-queue dependency entry is untouched.
  • Python needs no change: its version is VCS/tag-driven ([tool.hatch.version] source = "vcs"), so tagging v0.1.1 yields 0.1.1 automatically.

⚠️ Merge order

This must merge together with #43 (--allow-same-version) before cutting the release. Otherwise the v0.1.1 release re-hits "Version not changed", since package.json will already be at 0.1.1.

Release steps (after both merge)

  1. Create release/tag v0.1.1 → Python publishes to PyPI, JS publishes to npm.
  2. Verify npm view envoic version shows 0.1.1.

Summary by CodeRabbit

  • Chores
    • Updated the JavaScript package version from 0.1.0 to 0.1.1.

envoic@0.1.0 was previously published then unpublished on npm, so the
registry permanently refuses to republish 0.1.0 (the v0.1.0 release got
"Cannot publish over previously published version 0.1.0"). Bump the JS
package to 0.1.1 so it can ship and realign with PyPI.

The Python package needs no change: its version is derived from the git
tag (hatch source = "vcs"), so tagging v0.1.1 yields 0.1.1 automatically.
@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 22a9e422-18e4-4652-a2fc-895e5324f039

📥 Commits

Reviewing files that changed from the base of the PR and between 540df9b and c59f0f0.

⛔ Files ignored due to path filters (1)
  • packages/js/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • packages/js/package.json

📝 Walkthrough

Walkthrough

The version field in packages/js/package.json is bumped from 0.1.0 to 0.1.1.

Changes

Version Bump

Layer / File(s) Summary
Package version increment
packages/js/package.json
Version field updated from 0.1.0 to 0.1.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

A tiny hop, a patch so small,
From one-oh to one-one we crawl,
The version ticks, the bunny grins,
A minor bump is how progress begins! 🐇✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: bumping the JS package version to 0.1.1 for an npm release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/js-0.1.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mahimairaja mahimairaja self-assigned this Jun 30, 2026
@mahimairaja
mahimairaja merged commit aec9aea into main Jun 30, 2026
2 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.

1 participant