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.

Sign up for GitHub

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

Jump to bottom

Include only major version inside schema generation #1512

Closed
ssbarnea opened this issue May 3, 2023 · 0 comments · Fixed by #1513
Closed

Include only major version inside schema generation #1512

ssbarnea opened this issue May 3, 2023 · 0 comments · Fixed by #1513
Assignees
@shatakshiiii
Labels
bug Researched, reproducible, committed to fix

Comments

@ssbarnea
Copy link
Member

ssbarnea commented May 3, 2023

In order to avoid changing the schema on each navigator minor release, we should only include the major version in it, like Navigate v3 Schema. This would ease maintenance on linter, which sync schema on each build.
@ssbarnea ssbarnea added bug Researched, reproducible, committed to fix new New issues and PRs to triaged and removed new New issues and PRs to triaged labels May 3, 2023
@shatakshiiii shatakshiiii mentioned this issue May 3, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shatakshiiii shatakshiiii

Labels
bug Researched, reproducible, committed to fix
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Include only major version inside schema generation shatakshiiii/ansible-navigator
2 participants
@ssbarnea @shatakshiiii