Activity

Summary

Cuts v2.10.0 bundling #185 (closes #178). Minor bump for new schema surface area on the application tool — follows the v2.8.0 precedent for analogous application-field additions (#161 / #162).

What's in it

• Build-config wired through create_*: dockerfile_location, dockerfile_target_build, base_directory, publish_directory, install_command, build_command, start_command, watch_paths — previously declared in types but silently stripped on every create. Now forwarded by create_public, create_github, create_key. Intentionally excluded from create_dockerimage (pre-built images, no build step) per Coolify's controller allowlist.
• All 12 health_check_* fields wired through create_*: forwarded by all four create_* actions including dockerimage.
• dockerfile_target_build accepted on update: verified UPDATE-only via Coolify's ApplicationsController.php allowlists (update_by_uuid line 2497 includes it, create_application line 1014 does not).
• CLAUDE.md gotcha: documented the CREATE vs UPDATE \$allowedFields asymmetry and the fact that Coolify's openapi.yaml is an incomplete projection of the real controller allowlists. Live-verified against coollabsio/coolify main.

Verification

• 307 tests passing
• Codecov green
• Live-tested against Coolify v4 by @kashik0i on #185 (round-trip GET on every new field)

Triggers npm publish

Merging this changes package.json on main → publish.yml runs → @masonator/[email protected] publishes to npm via trusted publishing.

Test plan

• All 307 tests pass
• Prettier check clean on CHANGELOG / package.json / package-lock.json
• Confirm npm publish succeeds after merge