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

Transition from $id + $schema to just $schema, and versioning #287

Open
jaimergp opened this issue Dec 14, 2024 · 1 comment · May be fixed by #288
Open

Transition from $id + $schema to just $schema, and versioning #287

jaimergp opened this issue Dec 14, 2024 · 1 comment · May be fixed by #288

Comments

@jaimergp
Copy link
Contributor

Comes from #282 and #283.

We need to think how to transition existing schemas and make them pass validation. Maybe this is already the case, but needs to be assessed. There might not be too many published packages with menuinst v2 compat out there anyway.

This also brings the topic of versioning the schema via $schema, backwards compatibility, etc. menuninst will probably need to stay compatible with all previous schemas indefinitely.

Which versioning scheme should we use? Could be schemaver, or just good old semver.

Thoughts @conda/constructor @wolfv?

@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Dec 14, 2024
@jaimergp jaimergp linked a pull request Dec 14, 2024 that will close this issue
3 tasks
@jaimergp
Copy link
Contributor Author

I've opened #288 and chose 1-1-0 for the next release, and 1-0-* for the previous releases in menuinst v2.0, 2.1 and 2.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

1 participant