'versioning' 검색 결과

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management

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

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management

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

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management

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

Expert guide for designing robust APIs: REST best practices, GraphQL, gRPC, tRPC, OpenAPI/Swagger, API versioning, rate limiting, and contract-first design / Panduan ahli untuk merancang API yang kuat: praktik terbaik REST, GraphQL, gRPC, tRPC, OpenAPI/Swagger, versioning API, rate limiting, dan desain contract-first.

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

Design serialization schemas using JSON Schema, Protocol Buffer definitions, or Apache Avro. Covers schema versioning, backwards compatibility, validation rules, and evolution strategies for long-lived data formats. Use when defining a new API contract or data interchange format, adding fields to an existing schema without breaking consumers, migrating between schema versions, choosing between schema systems, or documenting data validation rules for automated enforcement.

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

Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or distributing build artifacts (binaries, tarballs).

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

Analyzes git commit history and generates professional changelogs with semantic versioning, conventional commit support, and multiple output formats (Keep a Changelog, Conventional, GitHub). Use when editing CHANGELOG.md, CHANGELOG.txt, or HISTORY.md files, preparing release notes, creating releases, bumping versions, updating changelog, documenting changes, writing release notes, tracking changes, version bump, tag release, or when user mentions "changelog", "release notes", "version history", "release", "semantic versioning", or "conventional commits".

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

Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).

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

Use when committing or pushing changes and the repository needs a version bump. Analyzes commits using conventional commit prefixes to determine whether the next release is a major, minor, or patch increment. Also use when the user asks about versioning, release planning, or changelog generation.

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

Large-scale data migrations with validation, rollback, and zero-downtime strategies. Activate on: data migration, database migration, zero-downtime migration, dual-write, backfill, cutover, data validation, schema migration. NOT for: schema evolution in streams (use schema-evolution-manager), API versioning (use api-versioning-backward-compatibility).

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

Use when designing or changing public C#/.NET APIs with compatibility and versioning constraints. Keywords: breaking change, API design, backward compatibility, binary compatibility, deprecation strategy, versioning.

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

Use on every code change — commit structure, branching, history hygiene, and versioning. Apply when committing work, opening or splitting a branch, writing commit messages, cutting a release, or recovering from a bad history state.

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

Expert en construction de design systems avancés (tokens, composants, Storybook, Figma sync, versioning, theming)

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

API Designer IA — Expert en conception d'APIs (REST, GraphQL, gRPC, OpenAPI, versioning, rate limiting). Crée des APIs intuitives, évolutives et sécurisées.

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

Expert en déploiement d'agents IA (containerisation, scaling, monitoring, versioning, A/B testing agents)

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

Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project

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

Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform

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

Provides expert knowledge for designing, implementing, and managing REST API versioning strategies with deprecation workflows.

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

Large-scale data migrations with validation, rollback, and zero-downtime strategies. Activate on: data migration, database migration, zero-downtime migration, dual-write, backfill, cutover, data validation, schema migration. NOT for: schema evolution in streams (use schema-evolution-manager), API versioning (use api-versioning-backward-compatibility).

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

Versions HTTP APIs. Asp.Versioning.Http/Mvc, URL segment, header, query string, sunset.

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

Handle an explicit Git intent such as branch/worktree setup, commit organization, history archaeology, conflict resolution, PR preparation, or versioning; do not trigger as a process skill for every code or file change.

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

Automates releases and package publishing with changesets or semantic-release. Handles versioning, changelog generation, git tags, and release notes. Use for "release automation", "semantic versioning", "package publishing", or "changelog generation".

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

혼합된 코드 변경을 목적별 커밋으로 나누고 브랜치와 PR 준비를 돕습니다. 호환성에 맞는 버전 번호와 변경 기록을 정리하고 커밋 전 점검도 다룹니다.

• 혼합된 변경을 목적별 커밋으로 나눕니다
• 검토할 브랜치와 PR을 준비합니다
• git worktree로 병렬 작업을 분리합니다

Paperclip의 후보 버전 검증부터 npm 게시, GitHub Release 생성, 공지 후속 작업까지 관리하며, 검증된 canary 시험 버전을 안정 버전으로 승격합니다.

• Paperclip 전체 릴리스 진행 관리
• 검증된 canary를 안정 버전으로 승격
• Docker로 후보 버전 동작 확인