paketo-buildpacks / bionic-full-stack Goto Github PK

Create Release workflow failed.
Please take a look to ensure CVE patches can be released. (cc @paketo-buildpacks/stacks-maintainers).

Push Image workflow failed.
Please take a look to ensure CVE patches can be released. (cc @paketo-buildpacks/stacks-maintainers).

In #25 we re-added the multiverse package source to the stack images with the intention of enabling use cases that might need packages from this location.

We do not want to ship any packages from multiverse in the stacks themselves, as explained in the linked PR. To prevent against this in the future, we should add a test assertion to the suite that checks that no packages come from the multiverse repository.

Paketo Stacks RFC 0005 states the Paketo Bionic stacks should follow suit with recent organizational changes to naming, publishing, and repository set up implemented for the Paketo Jammy stacks.

This issue is to implement these changes for the Paketo Bionic Full stack:

• Create stack definition files (stack.toml and build/run Dockerfiles) similar to the ones for the Jammy Full stack. The same set of packages shipped in the existing Bionic Full stack should be used.
• Leverage the new workflows and actions
• Publish the generated stacks to both the old -cnb suffixed and non-cnb tags, as well as the new location outlined in the RFC:

   paketobuildpacks/{build/run}:{version}-full
   paketobuildpacks/{build/run}:{version}-full-cnb
   paketobuildpacks/{build/run}-bionic-full:{version}

• Remove the full-stack-release repo when these changes have been rolled out successfully.

Create Release workflow failed.
Please take a look to ensure CVE patches can be released. (cc @paketo-buildpacks/stacks-maintainers).

Hi, I notice that paketobuildpacks/build:full-cnb has been removed to paketobuildpacks/build-bionic-full:latest, I want to know if the paketobuildpacks/build:xxx will be deprecated later?
Because we will pull the image from the docker hub to our own service registry regularly， and currently the stack repo changed to
paketobuildpacks/build-bionic-full
paketobuildpacks/build-bionic-base
paketobuildpacks/build-bionic-tiny
paketobuildpacks/build-jammy-full
paketobuildpacks/build-jammy-base
paketobuildpacks/build-jammy-tiny

how do we follow the rename of the repo?

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

Motivations

The run image contains packages that are not useful and should be removed.

This is primarily ruby, but there could be other packages that should be removed, too.