- Порезанный
- 24 сентября 2026 г. в 19:20 UTC
- Автор
- Kamo
- Обещать
- c00fd0e
db737a54 moved the library to 1.6.2, and only emailservice and initializerservice moved with it. About thirty other services pin 1.6.1. Their CI clones this repo's main and installs it into a cold ~/.m2 (there is no remote registry), so after the bump 1.6.1 exists nowhere, and the next build of any of them fails with Could not find artifact **************** The bump is not what makes OrgAliasDomainEntity reachable: every CI build takes whatever main holds, so 1.6.1 carries the entity and its repository as well. emailservice and initializerservice go back to 1.6.1 in their own commits, and the estate has one version again. The library keeps a single version and it stays 1.6.1. Local builds: install this repo again after pulling (mvn -DskipTests install). A 1.6.1 installed before db737a54 has no OrgAliasDomainEntity.