feat: update to newer lifecycle and pack versions

[mhdawson]

Summary

update to newer version of lifecycle and pack

Use Cases

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).

[mhdawson]

Thanks to @natalieparellano who figured out the part about how to use the registry in the scripts.

I had to put the docker stop where it is as anywhere later and it did not seem to run. I suspect something to do with how the go test results are output but not sure.

[robdimsdale]

I had to put the docker stop where it is as anywhere later and it did not seem to run. I suspect something to do with how the go test results are output but not sure.

Yeah, the util::print::success and util::print::error functions exit after printing, so that makes sense. Ideally we would refactor this to be clearer (e.g. using trap or similar), but it should work for now.

More generally, can you help me understand why we now need a registry? What is different from the other builder tests that run directly against the docker engine?

[natalieparellano]

can you help me understand why we now need a registry

When extending images, we use kaniko, which requires a manifest (or more specifically, a v1.Image implementation) so we need the image to exist in a registry in order to pull the data.

[robdimsdale]

When extending images, we use kaniko, which requires a manifest (or more specifically, a v1.Image implementation) so we need the image to exist in a registry in order to pull the data.

Ah. I didn't realize that. So it would be more accurate to say that we have always needed a registry for this builder, we just hadn't added it yet.

[robdimsdale]

Also I think pack v0.30.0 just got released so we can fix this, too.

[mhdawson]

Updated, I assume it should be good, smoke tests run on PR should confirm.

[mhdawson]

@robdimsdale

Ah. I didn't realize that. So it would be more accurate to say that we have always needed a registry for this builder, we just hadn't added it yet.

Correct, except that because of an earlier bug in pack it at least seemed to run/work before.

[robdimsdale]

Ah ok. Thanks. I'm not as familiar with extensions so I'm just trying to follow along.