Skip to content
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.

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

[Backport v2.0] Don't allow v2 components to be added to v1 manifest #2028

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

itowlson
Copy link
Contributor

@itowlson itowlson commented Nov 2, 2023

Backporting #2025 to v2.0

Signed-off-by: itowlson <[email protected]>
(cherry picked from commit 62d86b1)
@itowlson itowlson requested a review from vdice November 2, 2023 02:55
@itowlson
Copy link
Contributor Author

itowlson commented Nov 2, 2023

@vdice I've put this in because it's something Mikkel raised and does not affect user or developer experience. But feel free to decline it if you want to keep 2.0 as frozen as possible - I'm completely sympathetic to that!

@vdice
Copy link
Member

vdice commented Nov 2, 2023

@itowlson I'm fine with backporting if you'd like to see it in. I didn't get a chance to test this logic -- is the error obvious to the user when they add a componnent with a mismatched manifest version?

@itowlson
Copy link
Contributor Author

itowlson commented Nov 2, 2023

@vdice I hope so. It prints Error: This template is for a different version of the Spin manifest - I admit this could be better but hopefully enough.

@vdice vdice merged commit 0ff259f into v2.0 Nov 2, 2023
9 checks passed
@vdice vdice deleted the backport-2025-to-v2.0 branch November 2, 2023 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants