Skip to content

chore(release): configure Editor V0 maintenance - #518

Draft
dancormier wants to merge 1 commit into
v0from
STACKS-856/configure-editor-v0
Draft

chore(release): configure Editor V0 maintenance#518
dancormier wants to merge 1 commit into
v0from
STACKS-856/configure-editor-v0

Conversation

@dancormier

Copy link
Copy Markdown
Contributor

Summary

  • configure v0 as the protected Editor 0.15.x maintenance line
  • publish maintenance releases under legacy-v0 without changing npm or GitHub Latest
  • reject versions outside stable 0.15.x and unsafe SemVer-like npm tags
  • add CODEOWNERS and release-configuration coverage
  • verified with build, lint, 1,092 unit tests, 195 Playwright tests, and six release-configuration tests
  • no product behavior or accessibility changes

Jira

STACKS-856

Release safety

V0 publication validates the package version and npm dist-tag before publishing. GitHub Release creation is disabled for this maintenance line.

Changeset

Not required. This configures release infrastructure without changing the published package.

@changeset-bot

changeset-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7334557

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant