chore: prepare 0.2.0 release

[sriramveeraghanta]

Description

Adds the changeset that releases @makeplane/propel@0.2.0, and fixes the two configuration defects that would otherwise have stopped it from publishing.

Why now: the currently published 0.1.0 is not installable. It shipped with unresolved pnpm catalog: specifiers in dependencies:

npm  → EUNSUPPORTEDPROTOCOL: Unsupported URL Type "catalog:"
pnpm → "This is likely a bug in the publishing automation of this package."

It was also published from a tree that isn't in this repo's history (gitHead 5ed8a3c9, attestations: null), five weeks before the first commit here. So 0.2.0 is effectively the first usable release.

Changes

• .changeset/tender-grapes-kneel.md — minor bump. Contents derived by diffing the published 0.1.0 tarball against the current dist, not from commit messages, since the published artifact came from a foreign tree. Adds the icons subpath (737 icons), button-group, split-button, expandable-search, components/icon, components/shortcut; removes menubar, meter, toggle-group. Removals are breaking, but propel is pre-1.0 so they ship in the minor slot.

• .github/workflows/release.yml — the release job ran on blacksmith-4vcpu-ubuntu-2404. Publishing authenticates via npm trusted publishing (OIDC) with no NPM_TOKEN fallback, and Blacksmith registers as a self-hosted runner (the job log says so: A job started hook has been configured by the self-hosted runner administrator). npm's docs: "Trusted publishing currently supports only cloud-hosted runners." Moved to ubuntu-latest. Also bumps pnpm/action-setup@v4 → v6 and actions/setup-node@v4 → v6 — a stale action-setup breaks the OIDC exchange (pnpm/pnpm#11513) and the v4s trigger the Node 20 deprecation warning. Deliberately no registry-url: on setup-node; it writes an .npmrc pinning _authToken=${NODE_AUTH_TOKEN}, which is empty on the OIDC path.

• .changeset/config.json — adds "privatePackages": false. The default (version: true) let changeset add offer the private workspaces; verified against a fixture that a changeset targeting docs bumped it 0.0.0 → 0.1.0 and wrote it a CHANGELOG. Now only @makeplane/propel is versionable.

• .changeset/README.md — documents the two-merge flow, the pre-1.0 bump table (major on 0.x ships 1.0.0), and that a green Release run is not evidence anything shipped.

Type of Change

• Bug fix (non-breaking change which fixes an issue) — release pipeline could not publish
• Feature (non-breaking change which adds functionality)
• Improvement
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media

Test Scenarios

• pnpm changeset status --verbose reports @makeplane/propel 0.2.0 under "Packages to be bumped at minor", and nothing else.
• On merge, the Release workflow opens a "Version Packages" PR bumping packages/propel/package.json to 0.2.0 and writing CHANGELOG.md. Nothing publishes at this step.
• Merging that Version Packages PR publishes 0.2.0 to npm with provenance, and creates the tag + GitHub release.
• After publish, npm install @makeplane/propel@0.2.0 succeeds in a clean directory (it fails today on 0.1.0), and the manifest shows real semver ranges rather than catalog:.
• import { AddOutline } from "@makeplane/propel/icons" resolves.

Blockers before merge

Two settings must be changed or this PR's merge produces a failed run:

1. Settings → Actions → General → Workflow permissions → enable "Allow GitHub Actions to create and approve pull requests". Currently can_approve_pull_request_reviews: false, so changesets/action cannot open the Version Packages PR.
2. npm trusted publisher for @makeplane/propel — org makeplane, repo propel, workflow release.yml. Never configured; 0.1.0 was a manual token publish.

Known issue not addressed here

tsdown.config.ts's banner callback fires for every emitted chunk, so "use client"; lands in 704 of 1442 .d.ts files — a TS1036: Statements are not allowed in ambient contexts for any consumer with skipLibCheck: false. publint and attw both pass; neither checks for it. Worth fixing before 0.2.0 rather than as a 0.2.1 follow-up.

References

• Releases @makeplane/propel@0.2.0
• Icons subpath originally added in [WEB-8236] feat: publish @makeplane/propel/icons subpath #2 (WEB-8236)
• pnpm/pnpm#11513 — pnpm publish via OIDC and stale action-setup
• npm trusted publishing docs

https://claude.ai/code/session_01Lk8E7Vv5ohN6pPBnnJTavu

[makeplane]

Linked to Plane Work Item(s)

References

• (WEB-8236) Propel Readiness: Icons

This comment was auto-generated by Plane