Merge canary into main to publish renamed packages to npm

[Copilot]

The main branch is missing the package renaming changes from PR #27 (merged to canary on Dec 2nd). Since release.yml only triggers on main, the renamed packages (htmldocs-v2-*) have never been published to npm.

Changes

This merge brings all commits from canary since Nov 29th:

• Package renaming: @htmldocs/* → htmldocs-v2-* prefix
  • htmldocs-v2-react
  • htmldocs-v2-render
  • htmldocs-v2-eslint-config
  • htmldocs-v2-typescript-config
• npm publication fixes: Set private: false and publishConfig.access: "public" for publishable packages
• Dependency updates: All internal workspace references updated to new names

Merge Conflicts Resolved

• apps/examples/package.json
• packages/htmldocs/public/template/package.json
• packages/react/package.json
• packages/render/package.json
• pnpm-lock.yaml

All conflicts resolved by accepting the canary (renamed) versions.

After Merge

The release.yml workflow will automatically publish packages to npm, enabling pnpx htmldocs-v2@latest init to work.

Original prompt

Problem

The canary branch contains critical package renaming changes (from @htmldocs/* to htmldocs-v2-*) that were merged on December 2nd, 2025 (commit 5b917cf4e2c9209419f6f28b7153243fb0897b00 from PR #27).

However, the main branch's last merge from canary was on November 29th, 2025 (commit 29aba5681fdb5eb29d1f8705cac99e5818ac5e07), which was before the package renaming changes.

This means:

• The renamed packages (htmldocs-v2-render, htmldocs-v2-react, etc.) exist in canary but not in main
• The release workflow (.github/workflows/release.yml) that publishes to npm only runs on pushes to main
• Users cannot install the packages because they haven't been published to npm with the new names

Solution

Merge all changes from the canary branch into the main branch. This will:

1. Bring the package rename changes to main (PR Rename @htmldocs/* packages to htmldocs-v2-* prefix for npm publishing #27 - "Rename @htmldocs/* packages to htmldocs-v2-* prefix")
2. Include any other commits made to canary since November 29th
3. Trigger the release.yml workflow when merged, which will:
   • Run pnpm run version to update package versions based on changesets
   • Run pnpm run publish to publish the renamed packages to npm
   • Use the NPM_TOKEN secret to authenticate

Expected Outcome

After this PR is merged to main:

• The GitHub Actions workflow .github/workflows/release.yml will automatically execute
• Packages will be published to npm with the correct names:
  • htmldocs-v2 (main CLI package)
  • htmldocs-v2-render (render package)
  • htmldocs-v2-react (react components package)
• Users will be able to successfully run pnpx htmldocs-v2@latest init without dependency resolution errors

Changes Included

This merge includes all commits from canary that are not yet in main, most notably:

• Package renaming from @htmldocs/* to htmldocs-v2-* scope-free names
• Updated dependencies to reference the new package names
• Fixed publishConfig and private flags for npm publication
• Any other bug fixes and improvements made to canary since Nov 29th

This pull request was created as a result of the following prompt from Copilot chat.

Problem

The canary branch contains critical package renaming changes (from @htmldocs/* to htmldocs-v2-*) that were merged on December 2nd, 2025 (commit 5b917cf4e2c9209419f6f28b7153243fb0897b00 from PR #27).

However, the main branch's last merge from canary was on November 29th, 2025 (commit 29aba5681fdb5eb29d1f8705cac99e5818ac5e07), which was before the package renaming changes.

This means:

• The renamed packages (htmldocs-v2-render, htmldocs-v2-react, etc.) exist in canary but not in main
• The release workflow (.github/workflows/release.yml) that publishes to npm only runs on pushes to main
• Users cannot install the packages because they haven't been published to npm with the new names

Solution

Merge all changes from the canary branch into the main branch. This will:

1. Bring the package rename changes to main (PR Rename @htmldocs/* packages to htmldocs-v2-* prefix for npm publishing #27 - "Rename @htmldocs/* packages to htmldocs-v2-* prefix")
2. Include any other commits made to canary since November 29th
3. Trigger the release.yml workflow when merged, which will:
   • Run pnpm run version to update package versions based on changesets
   • Run pnpm run publish to publish the renamed packages to npm
   • Use the NPM_TOKEN secret to authenticate

Expected Outcome

After this PR is merged to main:

• The GitHub Actions workflow .github/workflows/release.yml will automatically execute
• Packages will be published to npm with the correct names:
  • htmldocs-v2 (main CLI package)
  • htmldocs-v2-render (render package)
  • htmldocs-v2-react (react components package)
• Users will be able to successfully run pnpx htmldocs-v2@latest init without dependency resolution errors

Changes Included

This merge includes all commits from canary that are not yet in main, most notably:

• Package renaming from @htmldocs/* to htmldocs-v2-* scope-free names
• Updated dependencies to reference the new package names
• Fixed publishConfig and private flags for npm publication
• Any other bug fixes and improvements made to canary since Nov 29th

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.