Skip to content

DRV-22: Consistent property sync and release workflow#16

Merged
svc-finitelabs[bot] merged 7 commits into
mainfrom
fix/DRV-22-consistent-sync-pattern
Mar 26, 2026
Merged

DRV-22: Consistent property sync and release workflow#16
svc-finitelabs[bot] merged 7 commits into
mainfrom
fix/DRV-22-consistent-sync-pattern

Conversation

@svc-finitelabs
Copy link
Copy Markdown
Contributor

@svc-finitelabs svc-finitelabs Bot commented Mar 26, 2026

Summary

Aligns influxdb driver with the consistent patterns used across all OSS drivers.

Changes

  • Property sync: Replace hand-rolled SendUIRequest / GetDeviceProperties with SetDeviceProperties() utility from src/lib/utils.lua
  • Release workflow: Glob *.zip instead of hardcoded control4-influxdb.zip

Addresses DRV-22

@svc-finitelabs svc-finitelabs Bot force-pushed the fix/DRV-22-consistent-sync-pattern branch from 33ca4b7 to b9d1fec Compare March 26, 2026 01:58
@svc-finitelabs svc-finitelabs Bot changed the title DRV-22: Use SetDeviceProperties utility for consistent property sync DRV-22: Consistent property sync and release workflow Mar 26, 2026
@svc-finitelabs svc-finitelabs Bot force-pushed the fix/DRV-22-consistent-sync-pattern branch 2 times, most recently from f25063f to b641e2d Compare March 26, 2026 02:03
@svc-finitelabs
Copy link
Copy Markdown
Contributor Author

CI is green now. The original failure was on commit f25063f (pre-force-push) where the README didn't match CI's pandoc output. After the force-push to b641e2d, CI passed, but I inadvertently added a local pandoc-regenerated README commit that re-broke it (local vs CI pandoc wraps lines differently). Reverted that and we're back to clean.

Note: the Makefile's docs-readme target doesn't pin pandoc's --wrap or --columns, so the output is non-deterministic across pandoc versions. Worth adding --wrap=none or --columns=80 to the template at some point to prevent this class of issue.

- Use SetDeviceProperties utility for property sync (consistent with all drivers)
- Glob zip files in release workflow (no hardcoded repo name)
@svc-finitelabs svc-finitelabs Bot force-pushed the fix/DRV-22-consistent-sync-pattern branch from 556efee to 8943f86 Compare March 26, 2026 02:16
Comment thread CHANGELOG.md Outdated
OpenClaw added 2 commits March 26, 2026 07:12
Property sync already works in the released version — this change is
about consistency with the other drivers, not a bug fix.
The build regenerates README.md via pandoc, which wraps lines at ~72
columns. The changelog entry exceeded that limit, causing a dirty-tree
diff in CI.
@svc-finitelabs svc-finitelabs Bot force-pushed the fix/DRV-22-consistent-sync-pattern branch from d1e735c to 3607203 Compare March 26, 2026 12:23
@svc-finitelabs svc-finitelabs Bot merged commit 6d62ba2 into main Mar 26, 2026
1 check passed
@svc-finitelabs svc-finitelabs Bot deleted the fix/DRV-22-consistent-sync-pattern branch March 26, 2026 14:06
svc-finitelabs Bot added a commit that referenced this pull request Mar 31, 2026
* DRV-22: Consistent property sync and release workflow

- Use SetDeviceProperties utility for property sync (consistent with all drivers)
- Glob zip files in release workflow (no hardcoded repo name)

* fix: update changelog wording per review feedback

Property sync already works in the released version — this change is
about consistency with the other drivers, not a bug fix.

* fix: pre-wrap changelog line to pass dirty-tree check

The build regenerates README.md via pandoc, which wraps lines at ~72
columns. The changelog entry exceeded that limit, causing a dirty-tree
diff in CI.

* fix: reset README.md (auto-generated by build)

* chore: regenerate README after build

* fix: revert changelog entry per review — user-facing changes only

* fix: remove Unreleased changelog section — no user-facing changes

---------
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