chore: promote nebari-frames to beta#45
Merged
Merged
Conversation
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
1 participant
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.
Promotes the pack to beta per the release readiness checklist. Evidence for the beta rows landed through #35's sub-issues, all closed: install and NebariApp health gated in CI on every PR (including the sandbox e2e), kubeconform schema validation (#40), structured JSON logging plus the telemetry justification (#39), documentation rows (#38 and the docs site at https://packs.nebari.dev/nebari-frames/ via #41/#43/#44), examples referencing the published Helm registry chart (#37), and a completed release pipeline with v0.1.5 published (chart on quay OCI, images on ghcr and quay, CLI on the brew tap). Live auth spot check: unauthenticated and bad-token requests to the API return 401 on the dev cluster. EffVer: v0.1.5 already follows the beta tag shape. Pre-sales demo sign-off and reviewer approvals obtained per the promotion process (pack owner, pre-sales rep, tech lead). last_promoted_pr is set to this PR's number in the follow-up commit. Closes #34, closes #35.