Skip to content

ci: require version bump when OpenMetrics 2.0 spec changes - #3115

Open
jarqvi wants to merge 1 commit into
prometheus:mainfrom
jarqvi:ci-om-spec-version-check
Open

jarqvi wants to merge 1 commit into
prometheus:mainfrom
jarqvi:ci-om-spec-version-check

Conversation

@jarqvi

@jarqvi jarqvi commented Sep 18, 2026

Copy link
Copy Markdown

Fixes #3087

Adds a CI step to the existing check-abnf job that fails when
docs/specs/om/open_metrics_spec_2_0.md changes without its - Version:
line changing. The new check_openmetrics_spec_version.py script compares
the version between the PR head and its merge base with the target branch.

Can be run locally:
python3 openmetrics-spec-tests/check_openmetrics_spec_version.py origin/main HEAD docs/specs/om/open_metrics_spec_2_0.md

Signed-off-by: MohammadHasan Akbari <jarqvi.jarqvi@gmail.com>
@roidelapluie

Copy link
Copy Markdown
Member

What if changes are only typos etc?

@jarqvi

jarqvi commented Sep 21, 2026

Copy link
Copy Markdown
Author

What if changes are only typos etc?

Yeah, right now even a typo fix would need a bump. How about a label
(something like skip-spec-version-check) that skips the check for cases
like that? Would that work for you?

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.

ci: Validate if spec change is bumping version on main branch

2 participants