Files
msime-windows/server/.github/workflows
Evan 54f0a404bf chore: advance the engine, check submodules daily, and auto-merge inert bumps (#28)
* chore: advance the engine submodule to current main

Six commits, none of them C++: an AGENTS.md, a README update, and the vcpkg
git-registry change that this repository already took for itself in #18.
git diff --name-status over the range lists exactly AGENTS.md, README.md and
vcpkg-configuration.json, so the engine's behaviour is unchanged.

The engine's vcpkg-configuration.json has no effect here: manifest mode reads
only the top-level manifest, and this repository has its own.

* chore(deps): check submodules daily instead of monthly

The gitsubmodule ecosystem was on a monthly schedule while MSIME-Engine takes
around fifteen commits a day. Dependabot has opened zero submodule PRs here so
far, so every engine pin move has been noticed and written by hand, which is
the whole reason the three frontends kept drifting onto three different engine
commits.

Daily turns that into one PR per submodule per day at most. The github-actions
ecosystem stays monthly; action pins do not move nearly as often.

* ci: let inert engine bumps merge themselves

Dependabot now checks submodules daily, which would mean roughly one engine
bump PR per repository per day. Most of them carry nothing that can change
behaviour: MSIME-Engine takes around fifteen commits a day and a large share
are documentation, CI wiring and dependency manifests.

This workflow classifies the engine range on a dependabot bump and enables
auto-merge only when every changed file is provably inert. Everything else gets
a needs-review label and a comment naming the files that held it back.

The rule is an allowlist rather than a blocklist, and that distinction is the
point. Today Apple pinned an engine range whose only non-documentation entries
were CMakeLists.txt, .gitmodules and a bare utfcpp submodule pointer. A
blocklist keyed on source extensions would have waved the utfcpp bump through,
because a nested submodule appears in the compare API as a bare path with no
extension and no patch. The allowlist holds it.

Verified the classifier against both real ranges before committing: f91cd20 ->
main is inert as expected, and 8cc306c -> main is held with CMakeLists.txt,
.gitmodules and utfcpp named as the reasons.
2026-09-05 21:42:17 +09:00
..