Дата публикации: 20-05-2026 14:26:43

This morning I got hit with an error during a pipeline that the build failed policy enforcement due to ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. I’ve tried modifying rules in the pnpm-lock.yml file to change the time value but no avail.
After reading policy documentation this may be something enforced at the CircleCI global level? However, I’m not on a plan where I can manage these settings.
What’s frustrating/concerning is that it seems CircleCI may be enforcing their own standards for policies but not allowing all customers to have a way to change them without paying more. This is highly unusual practice and is creating a concern that CircleCI is implementing functionality to drive customers to higher tiers for monetary gain - which is normal - but in a way that breaks the functionality of the service at lower levels (not normal!).
Is there a way to fix this issue (change value of timeout or disable this policy requirement) without enabling policy management service level upgrade?
Hoping that I’m just missing additional details and that it’s not my paranoia kicking in.
2 posts - 2 participants
Read full topic

Основное содержимое страницы с новостью.

Схожие новости