skills.rest
datagouv
datagouvOFFICIAL
Explore all skills by this author →
Website𝕏@datagouvfrGitHub

bump-version

Create new API endpoint versions while preserving legacy YAML entries.

13|8|Updated Apr 2, 2026
Search Tags:#automation#devops#yaml#api-endpoints#bump-version#endpoint-versioning
One-click install
npx skills add https://github.com/datagouv/apistration --skill bump-version-datagouv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/datagouv/apistration/tree/main/site/.claude/skills/bump-version
Command: npx skills add https://github.com/datagouv/apistration --skill bump-version-datagouv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bump a version of an API endpoint fiche while preserving the previous version as legacy, enabling a smooth transition for consumers across API Entreprise and API Particulier.

Core Features & Use Cases

  • Create a new versioned endpoint entry with a bumped path (e.g. /vN/...).
  • Preserve the original (legacy) entry and link it via old_endpoint_uids/new_version anchors to maintain historical integrity.
  • Ensure documentation consistency by maintaining an updated historique and YAML anchors for shared fields.

Quick Start

Create a new vN endpoint entry and its corresponding legacy vN-1 entry in the endpoints config.

Frequently Asked Questions about bump-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new API version while preserving the legacy endpoint?▼

To create a new API version while preserving the legacy endpoint, identify the source endpoint fiche and generate a new versioned entry. This process maintains the original entry and links them via YAML anchors to ensure historical integrity.

How does endpoint versioning work for API Entreprise and API Particulier YAML files?▼

Endpoint versioning for API Entreprise and API Particulier works by applying a new_version tag and bumping the path in YAML config files. It enforces proper old and new endpoint linkages using YAML anchors and aliases to preserve the legacy fiche.

Do I need a PR or issue reference to bump an API endpoint version?▼

Yes, you need a PR or issue reference to bump an API endpoint version. This reference is required for traceability when creating a new versioned endpoint entry and preserving the original legacy entry in the endpoints configuration.

What is the best way to maintain documentation consistency when bumping API paths?▼

The best way to maintain documentation consistency when bumping API paths is by updating the historique and utilizing YAML anchors for shared fields. This ensures proper linkage between old and new endpoint versions across configuration files.

Can I use this versioning process for endpoints outside of config/endpoints/?▼

No, this versioning process applies specifically to API Entreprise and API Particulier endpoint YAML files located in config/endpoints/. It enforces path bumps and endpoint linkages only within this defined directory structure.

Related Skills

Explore More Software Engineering Skills→
jason-c-devjason-c-dev
1

aws-observability-setup

Configures CloudWatch, CloudTrail, AWS Config, and Security Hub across accounts and regions.

Community
Intermediate
dobrinz123dobrinz123

gsd-ship

Push branches, create pull requests, and monitor merge status.

Community
Intermediate
datagouvdatagouv
13

edit-endpoint

Edit API endpoint documentation and swagger definitions in the catalog.

Official
Advanced
mktkhrmktkhr

openapi-editor

Edit OpenAPI specifications and trigger Make-based code generation.

Community
Intermediate