Advance to 1.1.9-SNAPSHOT after releasing 1.1.8

[kevinherron]

Advance development to 1.1.9-SNAPSHOT after releasing 1.1.8.

Also change the Maven Release workflow from release.created to release.published. Publishing a saved draft does not emit created; published starts deployment for that path and was used for the 1.1.8 release.

The three incubating modules retain their separate 0.1-SNAPSHOT versions and deployment exclusions.

Validation: formatting, clean compilation, and full reactor verification passed on both the base and the 1.1.8 candidate (2,411 tests each, zero failures/errors, three skipped). Formatting and clean compilation also passed at 1.1.9-SNAPSHOT. Release deployment succeeded, and all 14 published coordinates were checked on Maven Central.

[greptile-apps]

Confidence Score: 5/5

[High risk] Bumps version numbers across the build system.

The PR appears safe to merge.

Summary

Advances the Maven reactor to 1.1.9-SNAPSHOT and starts release deployment when a GitHub release is published rather than created.

• Keeps the incubating modules’ separate versions and deployment exclusions.
• No actionable issue was identified.

_{Reviews (1) · Last reviewed commit: "Set version to 1.1.9-SNAPSHOT"}