Pete Brumm

@gvn182 @ricardovj @brianbroderick @mnj93 @tibbon if you get a chance, I think this pr may fix the issue. https://github.com/thiagopradi/octopus/pull/544 we are just getting started testing, but I can no longer...

sorry for the delay. I didn't see anything in syslog around this.

Would it be possible to clarify the license for this gem?

I got past it by rolling back to prior versions. that won't last long. - build - - '--builder' - 'paketobuildpacks/builder:full' - '--verbose' - '--env-file' - '/workspace/env_variables' - '--buildpack' -...

those 4 libs changed today and must have pushed it past the limit.

I am wondering if it is related to this change. the ca-certificates jumped from 3.6.7 to 3.8.3 https://github.com/paketo-buildpacks/nodejs/commit/91996d199e37e80ce1299dd39bd2877d7c825ace#diff-ac294531171abf4d8779df7ea98b67560755c4e8329248e8b627624078011f6dL36 here is the diff https://github.com/paketo-buildpacks/ca-certificates/compare/v3.6.7...v3.8.3

I can't work around this at this point. so I am blocked. from the looks of it. something is causing nodejs to get added multiple times. `Step #2: Buildpack 'paketo-buildpacks/[email protected]'...

This is a very basic rails 7 project that is just using the default settings and is using node and yarn to compile the assets after the updates above it...

I have had to transition my project away from paketo and to a custom docker setup. I would guess that the issue was related to including .npmrc and .yarnrc for...

The challenge and complexity I ran into was that once it is broken there is no moving forward unless it is resolved by paketo. the automated first of the month...