Results for “versioning”

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。

The English summary is being prepared. Showing the original description.

Work on the Android app — the thin WebView wrapper in `android/`. Use this whenever a task touches the Kotlin sources, the Gradle build, the WebView shell, the native settings screen, LMS server auto-discovery, the JS↔native bridge, app strings/i18n, or the Android CI/lint. Covers the "shell only, UI lives on the web" principle, the debug/release signing split, the static versioning F-Droid needs, and the min/target SDKs, so changes fit the wrapper.

The English summary is being prepared. Showing the original description.

Assigns pathogen lineages (SARS-CoV-2 Pangolin via UShER mode; Nextclade clade + QC; pango-designation alias_key.json resolution) and tracks variant frequencies over time using Nextstrain (Augur + Auspice), wastewater deconvolution (Freyja, COJAC, alcov, lineagespot), lineage fitness modelling (Wenseleers / Bedford-Figgins multinomial logistic), and recombinant detection (3SEQ, RDP4, Bolotie). Covers Pangolin pangolin-data version pinning (mandatory for reproducibility), Nextclade dataset versioning (lineage-defining mutations change with dataset), Freyja barcode forward-only date constraint, ARTIC primer scheme version churn (V3 / V4 / V4.1 / V5.3.2 / Midnight 1200) with documented dropout regions, recombinant X-prefix Pango designation lag, GISAID vs INSDC dual-deposition tensions, and the Karthikeyan 2022 wastewater early-detection signal with explicit reproducibility caveats. Use when assigning Pango lineages and Nextclade clades to viral consensus sequences, building Nextstrain Augur surveillance pipelines, deconvolving wastewater pooled samples into lineage frequencies with Freyja, tracking lineage frequencies and growth advantages over time, pinning pangolin-data / Nextclade dataset versions for reproducibility, handling ARTIC primer dropouts (V4.1 amplicons 64 / 76 / 88-90), or running variant surveillance for SARS-CoV-2 / influenza / Mpox / RSV / H5N1 / measles.

The English summary is being prepared. Showing the original description.

Use when generating REST controllers, response wrappers, DTOs, error handlers, or any HTTP-facing code. Defines response envelope, HTTP status mapping, pagination, and versioning.

The English summary is being prepared. Showing the original description.

Use when creating database migrations, schema changes, seed data, or any SQL that modifies database structure. Covers Flyway naming conventions, versioning, and safe migration patterns.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Step through versioning, tagging, and verification

The English summary is being prepared. Showing the original description.

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

The English summary is being prepared. Showing the original description.

Execute AEM Edge Delivery Services admin operations - list admins, add/remove users, preview, publish, unpublish content, clear cache, sync code, reindex, generate sitemap, manage snapshots, view logs, manage jobs, list sites, configure org/site settings, manage secrets and API keys. Also supports Document Authoring (DA) operations via admin.da.live - list/get/put content, copy, move, delete, versioning, and DA-specific preview/publish. Use for any Edge Delivery Services administrative task.

The English summary is being prepared. Showing the original description.

Deliver multi-file changes in thin vertical slices — implement, test, verify, commit, repeat. Load when implementing a feature from a plan, building across more than one file, refactoring, or when tempted to land a large change in one pass. Also triggers on "incremental implementation", "vertical slice", "thin slice", "one slice at a time", "don't do it all at once". Routes single-file fixes to direct execution. Pairs with test-driven-development and git-workflow-and-versioning.

The English summary is being prepared. Showing the original description.

Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.

The English summary is being prepared. Showing the original description.

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Assigns pathogen lineages (SARS-CoV-2 Pangolin via UShER mode; Nextclade clade + QC; pango-designation alias_key.json resolution) and tracks variant frequencies over time using Nextstrain (Augur + Auspice), wastewater deconvolution (Freyja, COJAC, alcov, lineagespot), lineage fitness modelling (Wenseleers / Bedford-Figgins multinomial logistic), and recombinant detection (3SEQ, RDP4, Bolotie). Covers Pangolin pangolin-data version pinning (mandatory for reproducibility), Nextclade dataset versioning (lineage-defining mutations change with dataset), Freyja barcode forward-only date constraint, ARTIC primer scheme version churn (V3 / V4 / V4.1 / V5.3.2 / Midnight 1200) with documented dropout regions, recombinant X-prefix Pango designation lag, GISAID vs INSDC dual-deposition tensions, and the Karthikeyan 2022 wastewater early-detection signal with explicit reproducibility caveats. Use when assigning Pango lineages and Nextclade clades to viral consensus sequences, building Nextstrain Augur surveillance pipelines, deconvolving wastewater pooled samples into lineage frequencies with Freyja, tracking lineage frequencies and growth advantages over time, pinning pangolin-data / Nextclade dataset versions for reproducibility, handling ARTIC primer dropouts (V4.1 amplicons 64 / 76 / 88-90), or running variant surveillance for SARS-CoV-2 / influenza / Mpox / RSV / H5N1 / measles.

The English summary is being prepared. Showing the original description.

Managing third-party dependencies — version pinning, security auditing, license compliance, update workflows, lockfile management, supply chain security. Activate on "npm audit", "dependabot", "renovate", "pin versions", "dependency update", "supply chain", "license compliance", "lockfile", "security advisory", "typosquatting", "SBOM". NOT for internal monorepo package management (use monorepo-management) or publishing your own packages to npm/PyPI.

The English summary is being prepared. Showing the original description.

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).

The English summary is being prepared. Showing the original description.

Expert knowledge of Flyway database migrations in melosys-api (Oracle DB). Use when: (1) Creating new database migrations, (2) Understanding migration versioning and naming, (3) Debugging migration failures, (4) Understanding Oracle-specific SQL patterns, (5) Adding tables, columns, or indexes. Triggers: "create migration", "new Flyway migration", "add column/table/index", "Flyway error", "checksum mismatch", "ORA-00955", "ORA-02292", "ORA-01430", "migration failed", "validate failed".

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.