Add new function runtimes to prepare for obsolete removals - #263
Merged
Merged
Conversation
Neal Morris (Nealm03)
changed the title
This changeset is a preparatory change to add new supported runtimes. Inspecting the scope of changes revealed that we have scattered logic and references to accepted runtimes. In addition, one of the misnomers in the CLI is how we refer to "deprecation". Previously, a "deprecation" date would throw an error, which behaviourally is more akin to an obsolete lifecycle stage. This changeset creates an explicit stage for obsolete vs deprecated.
Neal Morris (Nealm03)
force-pushed
the
refactor/function-runtime
branch
from
September 11, 2026 08:43
ec5cf5a to
a568761
Compare
Bruno Rafael (aNickPlx)
previously approved these changes
Sep 11, 2026
This changeset extends the supported runtimes to open up migration options away from the current obsolete runtimes as well as introducing a deprecation notice for the obsolete runtimes. This will only apply to deploying new functions, but will eventually be removed completely in the upstream API and rejected.
Neal Morris (Nealm03)
force-pushed
the
refactor/function-runtime
branch
from
September 11, 2026 10:02
a568761 to
00884be
Compare
Bruno Rafael (aNickPlx)
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
The primary motivation behind this changeset is to drop obsolete runtimes from the supported functions product, with a sunset date aimed for the end of the year. Consumers are expected to use new runtimes when deploying new functions.
Refactor function runtime management & validation
This changeset is a preparatory change to add new supported
runtimes. Inspecting the scope of changes revealed that we
have scattered logic and references to accepted runtimes.
In addition, one of the misnomers in the CLI is how we
refer to "deprecation". Previously, a "deprecation" date
would throw an error, which behaviourally is more akin
to an obsolete lifecycle stage.
This changeset creates an explicit stage for obsolete vs deprecated.
Prepare for removal of obsolete runtimes.
This changeset extends the supported runtimes to open up
migration options away from the current obsolete runtimes as well as
introducing a deprecation notice for the obsolete runtimes.
This will only apply to deploying new functions, but will eventually
be removed completely in the upstream API and rejected.