Skip to content

chore: API lifecycle - fix some line breaks #1007

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2025
+20 −20
Merged

chore: API lifecycle - fix some line breaks #1007

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/master/learn/feature-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ Alpha features are off by default, and you must enable them by a feature flag, f
removal or breaking changes without notice**, and aren't considered ready
for use in production.

Sometimes alpha features require Crossplane to add fields to existing beta or GA
<!-- vale alex.Condescending = NO -->
Sometimes alpha features require Crossplane to add fields to existing beta or GA
API types. In these cases you must mark fields (for instance in their OpenAPI
<!-- vale alex.Condescending = YES -->
schema) as alpha and subject to alpha API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All alpha features should have an issue tracking their graduation to beta.

Expand All @@ -43,11 +43,11 @@ instructions for migrating to the next version. This may require deleting,
editing, and recreating API objects. The editing process may require some
thought. This may require downtime for applications that rely on the feature.

Sometimes beta features require Crossplane to add fields to existing GA API types. In
<!-- vale alex.Condescending = NO -->
Sometimes beta features require Crossplane to add fields to existing GA API types. In
these cases you must mark fields (for instance in their OpenAPI schema) as beta
<!-- vale alex.Condescending = YES -->
and subject to beta API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All beta features should have an issue tracking their graduation to GA.

Expand Down
8 changes: 4 additions & 4 deletions content/v1.19/learn/feature-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example
removal or breaking changes without notice**, and generally not considered ready
for use in production.

In some cases alpha features require fields be added to existing beta or GA
<!-- vale alex.Condescending = NO -->
In some cases alpha features require fields be added to existing beta or GA
API types. In these cases fields must clearly be marked (for instance in their OpenAPI
<!-- vale alex.Condescending = YES -->
schema) as alpha and subject to alpha API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All alpha features should have an issue tracking their graduation to beta.

Expand All @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting,
editing, and recreating API objects. The editing process may require some
thought. This may require downtime for applications that rely on the feature.

In some cases beta features require fields be added to existing GA API types. In
<!-- vale alex.Condescending = NO -->
In some cases beta features require fields be added to existing GA API types. In
these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta
<!-- vale alex.Condescending = YES -->
and subject to beta API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All beta features should have an issue tracking their graduation to GA.

Expand Down
8 changes: 4 additions & 4 deletions content/v1.20/learn/feature-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example
removal or breaking changes without notice**, and generally not considered ready
for use in production.

In some cases alpha features require fields be added to existing beta or GA
<!-- vale alex.Condescending = NO -->
In some cases alpha features require fields be added to existing beta or GA
API types. In these cases fields must clearly be marked (for instance in their OpenAPI
<!-- vale alex.Condescending = YES -->
schema) as alpha and subject to alpha API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All alpha features should have an issue tracking their graduation to beta.

Expand All @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting,
editing, and recreating API objects. The editing process may require some
thought. This may require downtime for applications that rely on the feature.

In some cases beta features require fields be added to existing GA API types. In
<!-- vale alex.Condescending = NO -->
In some cases beta features require fields be added to existing GA API types. In
these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta
<!-- vale alex.Condescending = YES -->
and subject to beta API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All beta features should have an issue tracking their graduation to GA.

Expand Down
8 changes: 4 additions & 4 deletions content/v2.0-preview/learn/feature-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example
removal or breaking changes without notice**, and generally not considered ready
for use in production.

In some cases alpha features require fields be added to existing beta or GA
<!-- vale alex.Condescending = NO -->
In some cases alpha features require fields be added to existing beta or GA
API types. In these cases fields must clearly be marked (for instance in their OpenAPI
<!-- vale alex.Condescending = YES -->
schema) as alpha and subject to alpha API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All alpha features should have an issue tracking their graduation to beta.

Expand All @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting,
editing, and recreating API objects. The editing process may require some
thought. This may require downtime for applications that rely on the feature.

In some cases beta features require fields be added to existing GA API types. In
<!-- vale alex.Condescending = NO -->
In some cases beta features require fields be added to existing GA API types. In
these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta
<!-- vale alex.Condescending = YES -->
and subject to beta API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All beta features should have an issue tracking their graduation to GA.

Expand Down
8 changes: 4 additions & 4 deletions content/v2.0/learn/feature-lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ Alpha features are off by default, and you must enable them by a feature flag, f
removal or breaking changes without notice**, and aren't considered ready
for use in production.

Sometimes alpha features require Crossplane to add fields to existing beta or GA
<!-- vale alex.Condescending = NO -->
Sometimes alpha features require Crossplane to add fields to existing beta or GA
API types. In these cases you must mark fields (for instance in their OpenAPI
<!-- vale alex.Condescending = YES -->
schema) as alpha and subject to alpha API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All alpha features should have an issue tracking their graduation to beta.

Expand All @@ -43,11 +43,11 @@ instructions for migrating to the next version. This may require deleting,
editing, and recreating API objects. The editing process may require some
thought. This may require downtime for applications that rely on the feature.

Sometimes beta features require Crossplane to add fields to existing GA API types. In
<!-- vale alex.Condescending = NO -->
Sometimes beta features require Crossplane to add fields to existing GA API types. In
these cases you must mark fields (for instance in their OpenAPI schema) as beta
<!-- vale alex.Condescending = YES -->
and subject to beta API constraints (or lack thereof).
<!-- vale alex.Condescending = YES -->

All beta features should have an issue tracking their graduation to GA.

Expand Down
Loading