chore: release 5.0.2 (#1181)

* chore: release 5.0.2

Promote the PER-8053 config-merge work from beta to stable.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* chore: publish stable to the latest dist-tag

Was publishConfig.tag=beta; a stable release must go to the latest npm tag.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

chore: release 5.0.2-beta.2 (#1179)

Bumps past the published v5.0.2-beta.1 (which shipped without the config-merge,
PR #1178) — npm versions are immutable so the fix ships as a new beta.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

chore: release 5.0.2-beta.1 (#1177)

chore: set publishConfig.tag to beta for the 5.0.2-beta.0 line (#1158)

The merged release PR bumped the version to 5.0.2-beta.0 but left
publishConfig.tag at 'latest', so the next `npm publish` would push
the beta to the latest dist-tag. Flip it to 'beta' for this release; a
follow-up will flip back to 'latest' when 5.0.2 stable ships.

chore: bump version to 5.0.1 and switch publishConfig tag to latest (#…

…1147)

Promotes the runtime fix for `pseudoClassEnabledElements` (PPLT-5013, PR #1133)
from `5.0.1-beta.0` to a stable `5.0.1` release. Updates `publishConfig.tag`
from `beta` to `latest` so npm publish lands on the default dist-tag.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chore: bump version to 5.0.1-beta.0 and add publishConfig for beta tag (

#1137)

⬆️ Bump version from 4.2.0 to 5.0.0 in package.json (#1051)

🔖 v4.2.0

🔖 v4.1.0

🔖 v4.0.0