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

add version to config file #13

Merged
merged 1 commit into from
Nov 21, 2022
Merged

add version to config file #13

merged 1 commit into from
Nov 21, 2022

Conversation

codeboten
Copy link
Collaborator

This change adds a version value to the configuration file. Fixes #11

Signed-off-by: Alex Boten aboten@lightstep.com

This change adds a version value to the configuration file. Fixes #11

Signed-off-by: Alex Boten <aboten@lightstep.com>
@@ -0,0 +1,2 @@
# include version specification in configuration files to help with parsing and schema evolution.
version: 0.0.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What would be the use case to bump the "patch number"?

I am used to have "patch" when versioning the config files. Usually it is only "major" or "major.minor" depending on how strict is the parser.

Copy link
Contributor

@pellared pellared Nov 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also I think it should be named scheme-version. version suggests that this is the version of the config.

@pellared pellared mentioned this pull request Nov 22, 2022
@jack-berg jack-berg mentioned this pull request Dec 5, 2022
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.

Include config schema version
3 participants