'bump' 검색 결과

Operational guide for the NV oOS Dependabot alert triage-and-remediation loop: querying open alerts via gh api, separating stale from genuinely vulnerable lockfile entries (default-branch forensics), deciding between safe in-major override bumps, scoped overrides, or deferred major migrations (npm pack signature diffing), regenerating the 13-lockfile tree, dismissing alerts with the right reason, GitHub issue housekeeping, and triaging the known CI failure modes. Use when asked to fix dependabot alerts, close out dependabot issues, bump vulnerable npm packages, or resume a dependabot session.

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

Cuts the next minor release of Prisma Composer: bumps the root package.json version, propagates it to every workspace package in lockstep, and opens a PR titled "chore(release): v<next-version>". When a maintainer merges the PR, the `Publish to npm` workflow runs automatically and ships the new version to npm under dist-tag `latest`, plus a matching GitHub Release with auto-generated notes. Use when a maintainer asks to "cut the next minor", "bump to the next version", "open a release PR", or "prepare a publish PR".

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

Use when working with Changesets — changesets version management covering changeset file inventory, pending version bump analysis, package release readiness, changelog generation status, and monorepo release coordination. Use when auditing pending changesets, investigating release blockers, reviewing version bump strategies, or managing multi-package release workflows.

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

Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.

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

CHANGELOG エントリ追加・バージョン計算。「CHANGELOG」「変更履歴」「changelog add」「version bump」「バージョン」「バージョンアップ」などのキーワードで自動適用。

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

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.

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

リリース単位（単一パッケージか monorepo か）を判定し，SemVer でバージョンを上げ（マニフェストと全参照箇所を整合），bump コミット・タグ・push・About 欄・GitHub Release までの文面を提案．承認後に一気に実行する．「リリースして」「公開して」「バージョンを上げて」など版を公にすることを求められたときに使う．記録するだけなら /capstone:commit を使う．

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

Cut a new semver release — bump all version strings via bump-version.ts, open a release PR, and after merge tag main and push. Use when cutting a release, tagging a version, shipping a build, or preparing a deployment. Trigger keywords - cut tag, release tag, new tag, cut release, tag version, ship it.

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

개발한 변경을 공유하기 전에 베이스 브랜치 병합, 테스트와 차이 검토를 진행합니다. 버전과 변경 이력을 갱신하고 커밋, 푸시, PR 생성까지 처리합니다.

• 완료한 변경으로 PR 생성
• 푸시 전 테스트와 리뷰
• 제출 전 베이스 브랜치 병합

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

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

Claude Code 플러그인의 설정 파일 버전을 통일하고 빌드 검증, 태그 생성, GitHub 릴리스와 변경 이력 생성을 거쳐 npm 공개까지 진행합니다.

• 변경 내용에 맞는 버전 결정
• 플러그인 설정의 버전 통일
• GitHub 릴리스와 변경 이력 생성

Prepare and publish standalone @cline/ui releases to npm, the package registry. Covers version updates, quality checks, production and preview channels, release verification, and the initial setup that lets GitHub Actions publish the package.

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

• Preparing a production UI package release
• Publishing a preview with an explicit prerelease version
• Checking tests and package contents before release

Prepare Cline CLI releases for npm, the package registry, by reviewing SDK changes, drafting release notes, updating versions and changelogs, and creating release tags. Guides checks and publication through GitHub Actions or an authenticated local machine.

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

• Drafting CLI release notes from relevant changes
• Updating the CLI version and changelog
• Publishing a tagged release through GitHub Actions

Prepare Cline desktop releases for stable, beta, or nightly testing. Coordinate release notes, matching version files, tags, and a GitHub Actions workflow that builds signed installers and manages automatic update feeds for release channels.

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

• Preparing a stable desktop release
• Publishing a beta alongside the stable app
• Creating signed nightly test installers

Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.

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

• Assess readiness before an npm release
• Check breaking changes and migration needs
• Review version bump recommendations

Update Codex's pinned V8 and rusty_v8 versions, synchronize build settings and checksums, and validate a release candidate. If validation fails, investigate upstream changes and adjust the affected build files to restore a working build.

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

• Update Codex's pinned V8 and rusty_v8 versions
• Update prebuilt artifacts and checksums
• Validate a V8 release candidate

Create diagrams that explain systems, workflows, and data relationships using a consistent brand style. The skill guides diagram selection, layout, and readability, with HTML, SVG, and PNG output and support for importing existing diagram formats.

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

• Explain system architecture
• Visualize workflows and team handoffs
• Restyle existing diagrams to match a brand

Organize open pull requests before a release, classify what to merge or defer, and track decisions in a resumable document. Guide review, merging, follow-up fixes, and closing requests already covered by other changes.

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

• Sort a backlog of pull requests before a release
• Prioritize bug fixes for the next version
• Resume interrupted reviews from a progress document

Draft release notes from commits, pull requests, and file changes since the latest release tag. Update the Unreleased section of CHANGELOG.md with a thematic narrative while preserving previous releases and leaving versions and tags unchanged.

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

• Keeping release notes current during development
• Summarizing changes before a pull request
• Preparing a changelog draft before release

Prepare a Cherry Studio release by checking changes against the published version, writing English and Chinese release notes, updating version metadata, and creating a release branch after review to start the build workflow.

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

• Preparing a patch, minor, or major release
• Preparing a beta or release candidate
• Writing release notes from final user-visible changes

Prepare and publish a core Hindsight release, then open a pull request for its changelog and announcement blog post. Covers version updates, package publication checks, and synchronization of the accompanying documentation references.

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

• Publishing a new core Hindsight version
• Preparing a release changelog and announcement
• Checking release tags and publication workflows

Guide Prisma 8 development by selecting task-specific references for data definitions, queries, migrations that change database structure, runtime setup, debugging, and upgrades. Check package versions and generated contract files before proceeding with implementation.

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

• Set up Prisma 8 or connect it to an existing database
• Edit data definitions and plan database migrations
• Write queries and configure database connections

Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.

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

• Migrating Pester tests one major version at a time
• Fixing tests broken by a Pester upgrade
• Updating legacy Should and Invoke-Pester syntax

Add or verify model support in SGLang's Rust processor so chat requests produce the same prompt text and token IDs as Python. Use reference-generated test cases to find differences in tools, reasoning settings, conversation history, and errors.

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

• Adding model support to sglang-processor
• Porting model rendering from sgl-router
• Rechecking prompt behavior after a Dynamo update