Template issue for repositories that have not reset `main` to `wip` post-release

[Kevsy]

Problem description

As of 14th October '25, only 14 of the Fall '25 APIs have reset their main version to wip.

Possible evolution

This issue proposes a template issue to be created in each repository that has not reset its main branch to wip/vwip

Start template ✂️

{{ISSUE_TITLE}} Reset API and test code version information in main branch to wip

Problem description

Per CAMARA Release Management API release guidelines all main branch OAS YAML and Gherkin .feature files must have the version wip, and a server URL containing vwip .

{{REPOSITORY_NAME}} currently includes the following files in its main branch that are not set to wip: {{LIST_OF_NON_WIP_API_YAML_FILES}}, {{LIST_OF_NON_WIP_TEST_FEATURE_FILES}}

Codeowner action required

Please raise a PR which:

• For OAS YAML files: changes info.version to wip and changes the version number in the servers.url path to vwip
• For Gherkin .feature files: changes the version to wip in the Feature: line, and uses version vwip in the resource URL.

✂️ End template

Alternative solution

Additional context

It may be the case that the repository codeowners have already created an issue/PR to make the change back to wip. In which case this template issue can be considered a duplicate (and a reminder!)

[Kevsy]

@hdamker as requested, please feel free to tweak the text

[tanjadegroot]

Need to add feature files.

[Kevsy]

Need to add feature files.

Updated - thanks!

[tanjadegroot]

Propose to change the issue title to

• Reset API and test code version information in main branch to wip

as this eventually better expresses the work done in the changelog

[Kevsy]

Propose to change the issue title to

• Reset API and test code version information in main branch to wip

as this eventually better expresses the work done in the changelog

Done 👍

[tanjadegroot]

Done with new issue camaraproject/project-administration#63