Skip to content

Remove cflinuxfs3 and python 3.10 - #1261

Open
benjaminguttmann-avtq wants to merge 2 commits into
masterfrom
remove-cflinuxfs3-and-python-3.10
Open

benjaminguttmann-avtq wants to merge 2 commits into
masterfrom
remove-cflinuxfs3-and-python-3.10

Conversation

@benjaminguttmann-avtq

Copy link
Copy Markdown

Thanks for contributing to the buildpack. To speed up the process of reviewing your pull request please provide us with:

  • A short explanation of the proposed change:

    • Drop EOL Python 3.10 + CFLinuxFS3.
    • Switch Default to Python 3.14
  • An explanation of the use cases your change solves

  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the master branch

  • I have added an integration test

@benjaminguttmann-avtq
benjaminguttmann-avtq force-pushed the remove-cflinuxfs3-and-python-3.10 branch from 940003f to cc1d39c Compare November 2, 2026 13:05
Refresh offline fixtures and Pipenv locks for Python 3.14, including a manylinux2014 pylibmc wheel. Document the default runtime migration and fixture wheel build procedure.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The default-runtime jump from Python 3.10 to 3.14 affects all unpinned applications, and native-dependency and monitoring-agent compatibility requires staging, integration, and BRATS validation unavailable in this review.

No open issues 🎉

What changed in this PR

This PR retires Python 3.10 and cflinuxfs3 support from the Python buildpack and makes Python 3.14 the default runtime. It also updates test fixtures and documents the migration impact for applications.

Changes:

  • Remove Python 3.10 and cflinuxfs3 dependencies from the manifest.
  • Update integration settings, runtime expectations, and fixture dependencies for Python 3.14.
  • Document the default-runtime change and stack migration requirements.
File Description
src/​python/​integration/​versions_test.go Test explicit Python 3.14 runtime selection.
src/​python/​integration/​init_test.go Default integration tests to cflinuxfs4.
src/​python/​brats/​brats_test.go Remove cflinuxfs3-specific database error expectations.
manifest.yml Remove retired dependencies and default to Python 3.14.
fixtures/​vendored/​transitive/​runtime.txt Select Python 3.14.
fixtures/​vendored/​transitive/​requirements.txt Refresh transitive-dependency fixture packages.
fixtures/​vendored/​simple/​requirements.txt Refresh vendored application dependencies.
fixtures/​vendored/​pipenv/​Pipfile.lock Update locked dependencies and Python requirement.
fixtures/​vendored/​pipenv/​Pipfile Update package pins and select Python 3.14.
fixtures/​util/​override_buildpack/​override.yml Remove cflinuxfs3 from the override fixture.
fixtures/​services/​sealights/​requirements.txt Update Flask in the SeaLights fixture.
fixtures/​services/​appdynamics/​requirements.txt Update application dependencies and AppDynamics agent.
fixtures/​pipenv/​Pipfile.lock Update locked dependencies and Python requirement.
fixtures/​pipenv/​Pipfile Update package pins and select Python 3.14.
fixtures/​miscellaneous/​hooks/​requirements.txt Update Gunicorn in the hooks fixture.
CHANGELOG Document runtime and stack migration requirements.

Review effort: Balanced

@stokpop

stokpop commented Nov 16, 2026

Copy link
Copy Markdown

Thanks for this! I checked out the PR head (14e6574) and ran the integration suite locally on the Docker platform, uncached and parallel, on both cflinuxfs4 and cflinuxfs5. Both passed with no failures and no skips, including the Sealights and AppDynamics specs and the default Python 3.14 and runtime.txt version specs. CI is green on the same commit. I also grepped the PR head and found no remaining cflinuxfs3 or Python 3.10 references.

@stokpop

stokpop commented Nov 16, 2026

Copy link
Copy Markdown

Thanks Copilot. The staging and integration validation it couldn't see was run: CI is green on the PR head, and the integration suite also passed locally on cflinuxfs4 and cflinuxfs5, including the default-version spec and the Sealights and AppDynamics agent specs. The default-runtime change is called out in the CHANGELOG with a pointer to pin a version. BRATS is disabled in the buildpacks CI, so it isn't part of the gate.

@stokpop stokpop left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants