Repository navigation
fix: reset API version to wip on main (fixes #39) - #42
Merged
Merged
Conversation
hdamker
requested review from
FabrizioMoggio,
chinaunicomyangfan and
fernandopradocabrillo
as code owners
May 5, 2026 07:09
Contributor
Author
|
@fernandopradocabrillo @FabrizioMoggio @chinaunicomyangfan Gentle reminder to approve and merge this PR ... it is currently blocking the onboarding of the repository to Release Automation and new Validation. |
Contributor
Author
|
Merge without approval from @camaraproject/most-frequent-location_codeowners to unblock #45 (bypass rules with admin permission) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
correction
What this PR does / why we need it:
Resets API version information on
maintowipafter the previous release, per the standard CAMARA post-release procedure.This is a mandatory prerequisite for the Release Automation roll-out: the framework requires
wip/vwipversions onmainso the release process can drive transitions to concrete versions on dedicated release branches.Two files updated, four lines:
code/API_definitions/most-frequent-location.yaml:info.version0.2.0→wip; server URLv0.2→vwipcode/Test_definitions/most-frequent-location.feature: line 1 Feature headerv0.2.0→vwip; line 17 resource URLv0.2→vwipWhich issue(s) this PR fixes:
Fixes #39
Special notes for reviewers:
Mechanical wip reset. No semantic changes.
Changelog input
Additional documentation
This section can be blank.