Skip to content

[release] Regenerate version PR to v0.5.0 — #271 is stale and drops the #268 changeset #272

Description

@sobechestnut-dev

Source: pre-release audit (planning session). Priority: release-blocker. This is the release finale — do it AFTER the audit-batch PRs land on dev.

Problem

The open Changesets version PR #271 ("release: version packages (lockstep)") is stale and under-versioned. Verified from its diff:

If merged as-is it would (a) ship the new public adapter camera API (setView/getCameraState/setCameraState) as a patch instead of a minor, and (b) leave the preset-views changeset orphaned on dev, silently dropped from release notes.

Also: #271 is MERGEABLE but mergeStateStatus: BLOCKED, and no checks reported on the changeset-release/dev branch — likely just branch-protection + CI-only-on-main, but confirm.

Action

After all audit-batch fixes land on dev (each adds its own changeset), regenerate the version PR (re-run the changesets version workflow / ensure the action re-runs on the latest dev) so it consumes all pending changesets and produces v0.5.0.

Acceptance criteria

PR theme

Release mechanics — not a themed PR; a release action gated on themes A–F landing first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions