Skip to content

Remove old prerelease caveats from cloud packages page #1252

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

Open
timsneath wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove old prerelease caveats from cloud packages page #1252

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
4 changes: 2 additions & 2 deletions _data/new-data/get-started/cloud-services/tertiary-content-cloud-native.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ tertiary_cards:
link_text: View on GitHub
link: https://github.com/grpc/grpc-swift
- name: Swift OTel
text: OpenTelemetry client built for Swift observability libraries. (pre-1.0 release)
text: OpenTelemetry client built for Swift observability libraries.
link_text: View on GitHub
link: https://github.com/swift-otel/swift-otel
- name: Swift Prometheus
text: Client for the Prometheus monitoring system, supporting counters, gauges and histograms.
link_text: View on GitHub
link: https://github.com/swift-server/swift-prometheus
- name: Swift OPA
text: Evaluate Open Policy Agent IR Plans compiled from Rego declarative policy. (pre-1.0 release)
text: Evaluate Open Policy Agent IR Plans compiled from Rego declarative policy.
Copy link
Member

@czechboy0 czechboy0 Dec 1, 2025

Choose a reason for hiding this comment

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

Swift OPA still is pre-1.0: https://github.com/open-policy-agent/swift-opa

Copy link
Contributor Author

@timsneath timsneath Dec 1, 2025

Choose a reason for hiding this comment

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

Oh, interesting. I know you're authoritative :) but I couldn't find any reference to it being still a pre-release.

In any event, I wonder if this really is the place to track its status -- any of the above URLs would probably a better place to describe its status, since they're the places that will get updated with a change?

Copy link
Member

@czechboy0 czechboy0 Dec 1, 2025

Choose a reason for hiding this comment

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

The project being pre-1.0 just means it doesn't have a stable API yet, so packages can't depend on it expecting a stable API for a few years.

Swift OPA doesn't appear to have any releases yet (https://github.com/open-policy-agent/swift-opa/releases), so the only way to depend on it would be branch: "main" which would prevent your package from being even tagged with a version, I believe (SwiftPM would reject it).

I think of production readiness as an orthogonal metric, some packages are solid even before 1.0, others need time to bake post-1.0. But our original note about the lack of 1.0 was to call out the lack of a stable API yet.

Whether we want to keep it I'm agnostic about, fine either way.

link_text: View on GitHub
link: https://github.com/open-policy-agent/swift-opa