Version Packages

[sriramveeraghanta]

Releases @makeplane/propel@0.2.0.

This is the changesets "Version Packages" PR. It was generated by the Release workflow on the merge of #5 — the workflow pushed this branch successfully but could not open the PR itself (GitHub Actions is not permitted to create or approve pull requests), so it's opened manually. The contents are entirely machine-generated by changeset version; nothing here was hand-edited.

Contents

File	Change
packages/propel/package.json	0.1.0 → 0.2.0
packages/propel/CHANGELOG.md	## 0.2.0 section prepended
.changeset/tender-grapes-kneel.md	consumed (deleted)

No other workspace was touched — docs and oxlint-plugin-propel are correctly excluded by the privatePackages: false added in #5.

⚠️ Merging this publishes to npm

Unlike #5, this merge is the actual release: changeset publish runs, 0.2.0 goes to the registry with provenance, and the tag + GitHub release are created.

Confirm before merging: the npm trusted publisher must be registered for @makeplane/propel — org makeplane, repo propel, workflow release.yml. Publishing authenticates purely via OIDC with no NPM_TOKEN fallback, and this path has never been exercised (0.1.0 was a manual token publish, attestations: null). If it isn't configured, the publish fails after the full build.

Why 0.2.0 matters

The published 0.1.0 is not installable — it shipped literal pnpm catalog: specifiers in dependencies, so npm install fails with EUNSUPPORTEDPROTOCOL and pnpm add reports it as a publishing-automation bug. 0.2.0 is the first release consumers can actually install.

Known issue shipping in this release

"use client"; is injected into 704 of 1442 .d.ts files, which is TS1036: Statements are not allowed in ambient contexts for consumers with skipLibCheck: false. Not fixed here — the changeset is already consumed, so it needs a follow-up 0.2.1, or hold this PR while a fix lands on main with its own changeset.

https://claude.ai/code/session_01Lk8E7Vv5ohN6pPBnnJTavu