Skip to content

One version, changelog and release for the watch app and the integration - #7

Merged
raetha merged 2 commits into
devfrom
try/one-version
Nov 3, 2026
Merged

raetha merged 2 commits into
devfrom
try/one-version

Conversation

@raetha

@raetha raetha commented Nov 3, 2026

Copy link
Copy Markdown
Owner
  • zepp-devkit.json: one component, kestrel, versioned by watch/app.json with custom_components/kestrel/manifest.json required to match; tag v<version>.
  • One root CHANGELOG.md (the two [Unreleased] sections merged, entries unchanged, grouped under Watch app and Home Assistant integration) and one DRAFT.
  • CI: release-plan --dev on dev; one release per version with the watch packages and kestrel.zip; dev pre-releases tagged v<version>-dev.<run> (old ha-v…-dev ones cleaned up); install page reads the newest v release.
  • Release notes and the test-build page cover both parts; docs, CLAUDE.md and README updated.

Pins zepp-devkit's dev commit with the new options; switches to the v0.2.0 tag once that's released. Nothing is released either way while DRAFT exists.


Generated by Claude Code

The watch app and the Home Assistant integration now share one version (CI
checks the three version files match), one CHANGELOG.md with entries grouped by
the part they change, one DRAFT, and one tag v<version> whose release carries
the watch packages and kestrel.zip. release-plan runs with --dev on dev, so the
expected next version needs only [Unreleased] there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y5FKGuxtPN9CKcP5GhjfJY
raetha added a commit to raetha/zepp-devkit that referenced this pull request Nov 3, 2026
### Added

- `release-plan --dev`: on a `dev` branch that holds the expected next
version, an `[Unreleased]` changelog section is enough; without `--dev`
(on `main` and pull requests into it) the version still needs its own
section.
- Components that ship together under one version: `same_version` in
`zepp-devkit.json` lists other version files (Zeus `app.json` or Home
Assistant `manifest.json`) that must hold the component's version, and
`tag` sets the tag format (for example `v{version}`, one tag and GitHub
release for the whole project).

### Internal

- CI hardening: a single `CI passed` check gates releases, and no job
keeps the workflow token on disk unless it pushes with git
(`persist-credentials: false`).

Needed by Kestrel's single version (raetha/zepp-kestrel#7) and, with
`--dev`, by the watch faces' expected-next-version policy. Backwards
compatible: a minor release.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01Y5FKGuxtPN9CKcP5GhjfJY)_

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y5FKGuxtPN9CKcP5GhjfJY
@raetha
raetha merged commit db100a4 into dev Nov 3, 2026
13 checks passed
@raetha
raetha deleted the try/one-version branch November 3, 2026 05:51
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.

2 participants