'versioning' 검색 결과

Ensure cross-service integration defines contracts, ownership, failure handling, versioning, and rollout/rollback expectations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage semantic version updates for rad-mem project. Handles patch, minor, and major version increments following semantic versioning. Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history). Creates git tags and GitHub releases. Auto-generates CHANGELOG.md from releases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Safely evolve shared contracts with consumer discovery, migration tests, versioning checks, and downstream spec cascade validation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Aws Service Catalog — aWS Service Catalog portfolio and product management. Covers portfolio administration, product versioning, provisioned product inspection, launch constraints, tag options, and sharing across accounts. Use when managing self-service IT catalogs, provisioning products, reviewing portfolios, or auditing product usage across an organization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Aws S3 — aWS S3 bucket analysis, storage class distribution, lifecycle policies, access patterns, and cost optimization. Covers bucket inventory, object metrics, versioning status, encryption audit, public access analysis, and intelligent tiering evaluation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage breaking API changes, migration guides, deprecation notices, and semver versioning. Use when introducing breaking changes, writing migration paths, updating changelogs, or releasing major versions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. This should trigger for requests such as Review or improve Micronaut @Controller REST APIs; Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor media types), ISO-8601 instants in DTOs, pagination/sorting/filtering, Bean Validation at the boundary, idempotency, ETag concurrency, HTTP caching, error handling, security, contract-first OpenAPI (OpenAPI Generator), controller advice, and problem details for errors. This should trigger for requests such as Review Java code for Spring Boot REST API; Apply best practices for Spring Boot REST API in Java code. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates RESTful API Controllers with proper routing, versioning, authorization, and MediatR integration. Follows REST conventions and Clean Architecture patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI repo versioning and changelogs via release-please — never edit CHANGELOG.md or pyproject version by hand. Use when the user asks about releases, version bumps, changelogs, or preparing a release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate release notes from merged PR history and commits. Categorizes changes by type and creates GitHub releases with semantic versioning. Use when the user asks to create a release or generate release notes (e.g., "リリースノート", "release note", "リリース作成"). Do NOT use for changelogs, commit summaries, or PR descriptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design model registries for AI versioning. TRIGGERS - Use when user needs help with ai-model-registry related tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stripe 決済プラットフォームリファレンス (API 2026-09-30.endive)。 PaymentIntents, Checkout, Payment Links, Elements, Link, Managed Payments, Subscriptions, Invoices, Connect (Accounts v2), Radar, Terminal, Tax, Issuing, Treasury, Capital, Financial Connections, Climate, Revenue Recognition, Crypto Onramp, stablecoin, Identity, Webhooks, Stripe CLI, idempotency, API versioning, pagination, error handling。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.