Scan hr.careers, and drop the frozen work-location CHECK

FeatureInitializerService
Shipped
September 3, 2026 at 10:01 PM UTC
Author
Kamo
Commit
6c4be99

Two changes, both required before the careers entities can reach the database. The @EnableJpaRepositories list is an explicit array while @EntityScan is wildcard, so leaving com.kamo.z.shared.hr.careers out of it aborts the context, NO runner executes, and the run still reports BUILD SUCCESS having applied nothing. That is the failure this line exists to avoid, and it is silent. **************** gains **************** TeamMember.location is @Enumerated(ORDINAL), so Hibernate froze a CHECK (0..2) when WorkLocationType had three values. FLEXIBLE was appended for the /hr/careers Arrangement field — appending relabels no stored row, but the frozen range refuses the new one, and ddl-auto never widens an existing check. Without the drop, setting a team member's work arrangement to Flexible fails with a 23514 naming a constraint nobody has heard of.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing