Release v1.19.0 breaks existing python functions

[mneagul]

The release v1.19 seems to break existing python "functions".

One the things noticed is that it tries to enforce poetry:

Paketo Buildpack for Poetry 0.10.0
  Resolving Poetry version
    Candidate version sources (in priority order):
      <unknown> -> ""
    Selected Poetry version (using <unknown>): 2.1.2
  Executing build process
    Installing Poetry 2.1.2
      Completed in 7.694s
  Generating SBOM for /layers/paketo-buildpacks_poetry/poetry
      Completed in 1ms
  Configuring build environment
    PYTHONPATH -> "/layers/paketo-buildpacks_poetry/poetry/lib/python3.12/site-packages:$PYTHONPATH"
  Configuring launch environment
    PYTHONPATH -> "/layers/paketo-buildpacks_poetry/poetry/lib/python3.12/site-packages:$PYTHONPATH"

Which in turn, correctly, results in:

Paketo Buildpack for Poetry Install 0.5.0
  Executing build process
    Running 'POETRY_CACHE_DIR=/layers/paketo-buildpacks_poetry-install/cache POETRY_VIRTUALENVS_PATH=/layers/paketo-buildpacks_poetry-install/poetry-venv poetry install --only main'
      Directory /workspace/fn for function does not seem to be a Python package
      Creating virtualenv service-xS3fZVNL-py3.12 in /layers/paketo-buildpacks_poetry-install/poetry-venv
      Updating dependencies
      Resolving dependencies...
      
      Directory /workspace/fn for function does not seem to be a Python package

The corresponding func.yaml is:

specVersion: 0.36.0
name: sentinel-1-slc-cdse-fetch
runtime: python
registry: harbor.dev.info.uvt.ro/rocs
namespace: functions
created: 2025-07-29T10:00:48.116352+02:00
invoke: cloudevent
build:
  builderImages:
    pack: ghcr.io/knative/builder-jammy-base:0.4.439-amd64
  builder: pack
  buildEnvs:
  - name: BP_CPYTHON_VERSION
    value: 3.12.*

L.E.

The project by itself contains only func.yaml, func.py, requirements.txt and (optionally) a Procfile.

[matejvasek]

As fallback for now, please try s2i builder (--builder=s2i).