homeiot/contact_sensor
1
0
Fork 0
Code Issues Pull requests Projects Releases 11 Packages 1 Wiki Activity Actions

dev #5

Merged
faicel merged 3 commits from dev into staging 2026-08-04 09:38:32 +00:00
Conversation 0 Commits 3 Files changed 20 +515 -82
faicel commented 2026-08-04 09:38:23 +00:00
Owner
Copy link

[0.2.1] - 2026-08-04

Changed

  • CI publish flow aligned with lis2dh12: Cargo.toml stays at stable X.Y.Z; dev tags vX.Y.Z-rc → forgejorc; staging is merge gate only; main tags vX.Y.Z → forgejo and creates release/X.Y for hotfixes.
  • Add: check-on-feature-branch.yml, create-tag-on-dev.yml, create-tag-on-main.yml, validate-branch-flow.yml; rewrite publish-on-tag.yml (shared central_ci checks, enable_tag_check: false on tag publish, cargo test --features std).
  • Add: scripts/check-version-sync.sh, resolve-cargo-registry.sh, release-branch-name.sh (+ unit tests).
  • Docs: .forgejo/README.md documents the release model; .cargo/config.toml adds forgejorc.
  • Remove: legacy publish-on-main.yml (inline publish + PAT-in-URL).
## [0.2.1] - 2026-08-04 ### Changed - CI publish flow aligned with lis2dh12: `Cargo.toml` stays at stable `X.Y.Z`; `dev` tags `vX.Y.Z-rc` → forgejorc; `staging` is merge gate only; `main` tags `vX.Y.Z` → forgejo and creates `release/X.Y` for hotfixes. - Add: `check-on-feature-branch.yml`, `create-tag-on-dev.yml`, `create-tag-on-main.yml`, `validate-branch-flow.yml`; rewrite `publish-on-tag.yml` (shared `central_ci` checks, `enable_tag_check: false` on tag publish, `cargo test --features std`). - Add: `scripts/check-version-sync.sh`, `resolve-cargo-registry.sh`, `release-branch-name.sh` (+ unit tests). - Docs: `.forgejo/README.md` documents the release model; `.cargo/config.toml` adds `forgejorc`. - Remove: legacy `publish-on-main.yml` (inline publish + PAT-in-URL).
[0.2.1] - 2026-08-04
Some checks failed
Run checks on feature branches / rust-crate-checks (push) Failing after 10s
Details
Run checks on feature branches / checks (push) Failing after 0s
Details
51bdf10021 
### Changed

- CI publish flow aligned with lis2dh12: `Cargo.toml` stays at stable `X.Y.Z`; `dev` tags `vX.Y.Z-rc` → forgejorc; `staging` is merge gate only; `main` tags `vX.Y.Z` → forgejo and creates `release/X.Y` for hotfixes.
- Add: `check-on-feature-branch.yml`, `create-tag-on-dev.yml`, `create-tag-on-main.yml`, `validate-branch-flow.yml`; rewrite `publish-on-tag.yml` (shared `central_ci` checks, `enable_tag_check: false` on tag publish, `cargo test --features std`).
- Add: `scripts/check-version-sync.sh`, `resolve-cargo-registry.sh`, `release-branch-name.sh` (+ unit tests).
- Docs: `.forgejo/README.md` documents the release model; `.cargo/config.toml` adds `forgejorc`.
- Remove: legacy `publish-on-main.yml` (inline publish + PAT-in-URL).
fix lint
All checks were successful
Run checks on feature branches / rust-crate-checks (push) Successful in 15s
Details
Run checks on feature branches / checks (push) Successful in 0s
Details
7e01b5e616
Merge pull request 'update_workflow' (#4) from update_workflow into dev
All checks were successful
Create tag on dev / tag_prerelease (push) Successful in 7s
Details
Publish release on tag / rust-crate-checks (push) Successful in 14s
Details
Publish release on tag / checks (push) Successful in 0s
Details
Publish release on tag / release_on_tag (push) Successful in 10s
Details
Create tag on dev / rust-crate-checks (push) Successful in 15s
Details
Create tag on dev / checks (push) Successful in 0s
Details
918278bd27 
Reviewed-on: #4
faicel merged commit 108580b054 into staging 2026-08-04 09:38:32 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
homeiot/contact_sensor!5
No description provided.