-
Notifications
You must be signed in to change notification settings - Fork 64
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
Fix schema version incompatibility with nodejs-basic
sample parent
#1590
Closed
1 task done
michael-valdron opened this issue
Jun 5, 2024
· 3 comments
· Fixed by nodeshift-starters/devfile-sample#45, nodeshift-starters/devfile-sample#46 or devfile/registry#416
Closed
1 task done
Fix schema version incompatibility with nodejs-basic
sample parent
#1590
michael-valdron opened this issue
Jun 5, 2024
· 3 comments
· Fixed by nodeshift-starters/devfile-sample#45, nodeshift-starters/devfile-sample#46 or devfile/registry#416
Labels
area/registry
Devfile registry for stacks and infrastructure
Comments
openshift-ci
bot
added
the
area/registry
Devfile registry for stacks and infrastructure
label
Jun 5, 2024
Sized issue based on duration it took me. Priority set as blocker due to it blocking from promoting community devfile registry staging to production. |
4 tasks
Need to change schema version under |
Changed approach to referencing the previous parent stack version due to OpenShift Dev Console incompatibility with devfile 2.2.2 spec: devfile/registry#415 (comment) |
michael-valdron
changed the title
Update schema version of
Fix schema version incompatibility with Jun 6, 2024
nodejs-basic
samplenodejs-basic
sample parent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which area is this issue related to?
/area registry
Issue Description
The
nodejs-basic
sample should update the schema version to2.2.2
to match the Node.js Runtimenodejs
parent stack which had updated the default schema version in devfile/registry#403.Acceptance Criteria
2.2.2
The text was updated successfully, but these errors were encountered: