feat(spec)!: reset Application contract to v1alpha1 - #203
Merged
Merged
Conversation
Adopt the Kubernetes-shaped onebox.run/v1alpha1 resource, publish and embed its schema, migrate all fixtures and docs, and remove the v1 compatibility surface. BREAKING CHANGE: onebox.run/v1, snake_case declarative fields, lowercase enum values, root workload shorthand, aliases, and fallbacks are no longer accepted.
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.
Closes #202
Summary
onebox.run/v1alpha1ApplicationBreaking changes
There is no fallback or backward compatibility. Existing v1 files must be explicitly rewritten. Rewriting invalidates config-bound plans and confirmations; stale staged artifacts must be regenerated.
Verification
just checkjust cijust e2e(Docker; 262.850s)