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

In #31 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.

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

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

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

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

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

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 Base stack:

• Create stack definition files (stack.toml and build/run Dockerfiles) similar to the ones for the Jammy Base stack. The same set of packages shipped in the existing Bionic base 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}-base
   paketobuildpacks/{build/run}:{version}-base-cnb
   paketobuildpacks/{build/run}-bionic-base:{version}

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