Skip to content

chore: release server 0.8.46, cli 0.10.36#880

Merged
vivek7405 merged 1 commit into
mainfrom
chore/release-server-0.8.46-cli-0.10.36
Jul 9, 2026
Merged

chore: release server 0.8.46, cli 0.10.36#880
vivek7405 merged 1 commit into
mainfrom
chore/release-server-0.8.46-cli-0.10.36

Conversation

@vivek7405

@vivek7405 vivek7405 commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Release the accumulated unreleased work on @webjsdev/server and @webjsdev/cli. Merging this adds the changelog/**.md files to main, which triggers release.yml to npm publish both packages and cut GitHub Releases.

@webjsdev/server 0.8.45 -> 0.8.46 (patch)

@webjsdev/cli 0.10.35 -> 0.10.36 (patch)

Not bumped (checked all published packages)

Notes

  • Both bumps are patch and stay within the existing ^0.8.0 / ^0.10.0 dependent caret ranges, so no dependent range edits.
  • package-lock.json resynced (it was stale on main). The diff is three workspace version lines: server -> 0.8.46 and cli -> 0.10.36 (the bumps), plus core 0.7.30 -> 0.7.32 correcting the lockfile to core's already-current package.json (core itself is NOT re-released; only the server and cli changelog files trigger a publish).
  • The lockstep wrappers (create-webjs, webjsdev) are intentionally NOT bumped here; release.yml owns them.

Changelogs: changelog/server/0.8.46.md, changelog/cli/0.10.36.md.

@vivek7405 vivek7405 self-assigned this Jul 9, 2026

@vivek7405 vivek7405 left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Release checks out. Both bumps are patch and stay inside the ^0.8.0 / ^0.10.0 dependent ranges, the changelogs match the real changes and their hashes resolve, and the not-bumped packages (core/mcp/intellisense only cosmetic casing + docs, ui only the nested website) genuinely carry nothing releasable. One thing I confirmed and noted in the body: the lockfile resync also corrects a stale core entry (0.7.30 to 0.7.32) to match core's already-current package.json, so core is not re-released, only server and cli publish. Clean.

@vivek7405 vivek7405 left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Confirmed the publish path: release.yml keys on added changelog/**.md files (--diff-filter=A), and the diff adds exactly two (server 0.8.46, cli 0.10.36), so only those publish. Frontmatter versions and counts match the bumped package.json files. Ready to merge.

@vivek7405 vivek7405 marked this pull request as ready for review July 9, 2026 14:00
@vivek7405 vivek7405 merged commit e8618ad into main Jul 9, 2026
10 checks passed
@vivek7405 vivek7405 deleted the chore/release-server-0.8.46-cli-0.10.36 branch July 9, 2026 14:01
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