Kaloyan DanchevandClaude Opus 4.6
cbea5a322f
Move trampoline files (boot-hook, watcher, overlay) into trampoline/ subdirectory. Add upstream Luma v2.3.1 source at repo root with our additions: - Page::Ha (4th nav tab) with placeholder empty state - HA tab config schema and default entity mapping (ha-home/) - Nav keys renamed: "home" → "start", new "ha" tab between Apps and Settings - All state.rs/view.rs/main.rs/tests.rs updated for 4-tab navigation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
# Changesets
|
|
|
|
Run `pnpm changeset` in a feature or fix branch, select `lg-luma`, choose a patch, minor or major
|
|
bump, and describe the user-facing change. Commit the generated Markdown file with the PR.
|
|
Documentation-only and maintenance PRs that do not need a release can omit a changeset.
|
|
|
|
PRs receive an updating Changesets status comment. It reports the requested version bump or
|
|
notes that no changeset was committed and no version bump is requested. Code or behavior changes
|
|
should include a changeset: patch for compatible fixes, minor for compatible features, or major
|
|
for breaking changes. The comment is informational and also works on fork PRs.
|
|
|
|
Merged changesets accumulate in the automated **Version Packages** PR. Its version command
|
|
updates `package.json`, `CHANGELOG.md`, `appinfo.json`, the root `Cargo.toml`, the `luma` entry in
|
|
`Cargo.lock`, and the versioned IPK examples in `readme.md`. Supporting Rust crates keep their
|
|
own versions. Do not run `pnpm version:release` in ordinary feature PRs.
|
|
|
|
The version PR receives the same CI checks as other PRs. Merging it into `main` publishes the
|
|
verified IPK and Homebrew feed after CI passes. Other merges and manual CI runs do not publish.
|
|
See [the release guide](../development.md#releases) for repository setup and details.
|