'release' 검색 결과

Coordinate a Claude Code plugin release by updating version numbers across manifests, checking the build, creating a Git tag and GitHub release, and regenerating the changelog. The workflow also publishes to npm and verifies the published version.

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

• Choosing a version increment for a plugin release
• Synchronizing versions across plugin manifests
• Creating a GitHub release and regenerating the changelog

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 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

Publishes oh-my-opencode through GitHub Actions, then checks package versions and release artifacts. Covers related packages, user-facing release summaries, and Discord announcements, reporting failures without starting code repairs during the release process.

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

• Publishing a patch, minor, or major release
• Releasing a specific prerelease version
• Checking related packages and platform binaries

Coordinate a new Remotion release, from authentication and builds to npm package verification and release notes. Promote packages to latest only after every package is downloadable, then prepare a GitHub release for approval.

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

• Building and publishing a new Remotion version
• Checking all npm packages before updating latest
• Preparing release notes from commits and pull requests

Guide AAS maintainers through pull request review, batch merging, generated-file synchronization, and scripted releases. Follow protected-branch procedures and check evidence tied to the exact revision before accepting changes.

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

• Reviewing and merging a batch of pull requests
• Synchronizing generated files after source changes
• Preparing and publishing a protected release

Prepare a specified software version for release by checking version consistency and changelog readiness, building packages, and testing basic behavior. Produce checksums, release notes, and a readiness report; public release actions require separate authorization.

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

• Check version consistency and changelog readiness
• Build release packages and test basic behavior
• Prepare checksums and release notes

Prepare an AionUi release by checking AionCore assets, updating versions, and generating a changelog. Run quality checks, create a pull request with automatic merging enabled, then tag the merged release to trigger its build.

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

• Releasing the next AionUi patch version
• Releasing with explicitly chosen UI and Core versions
• Preparing a frontend-only release

Turn Git history into release notes and recommend the next version based on commit types and breaking changes. Check commit formatting, filter changes by package, and generate Markdown or JSON for automated release workflows.

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

• Prepare release notes before publishing a version
• Determine the next version from commit history
• Check commit message formats before merging

Checks published OpenWork desktop downloads for mac-arm64, verifying developer signatures, Apple notarization, and update metadata. It checks versions, download references, and file hashes, then records evidence to support a release rollout decision.

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

• Checking signatures and notarization on published downloads
• Verifying update versions, asset references, and hashes
• Recording release verification evidence in a PR or issue

Prepare and create a signed NemoClaw release tag for a requested version, then monitor release workflows, documentation, and published images. It records maintainer decisions and drafts an announcement after verifying the remote tag.

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

• Preparing a tag for a requested release version
• Recording documentation and end-to-end test decisions
• Checking workflows and images after tagging

Edit patch release notes for GitHub Enterprise Server, correcting typos and style while preserving approved technical facts. Keep repeated notes consistent across versions and update known issue source comments so future releases inherit the same edits.

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

• Proofread approved patch release notes
• Keep repeated notes consistent across versions
• Update source comments for known issues

Draft release notes from merged pull requests for releases that have already shipped. The skill filters internal changes, groups user-facing updates, matches the existing changelog style, and opens a pull request for human review.

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

• Draft release notes for a published tag
• Keep a changelog current through scheduled checks
• Catch up on several undocumented releases

Turn a structured change list into a categorized release notes draft for users. Follow the project's writing style, highlight breaking changes and security items, and include upgrade guidance where evident, leaving publication to human review.

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

• Drafting release notes from a structured change list
• Organizing features and bug fixes for users
• Highlighting breaking changes and security updates

Prepare and coordinate Octop Python package releases, including version updates, a Chinese changelog, and a pull request. After merging, GitHub Actions handles release tags, package and container publishing, and branch synchronization.

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

• Preparing an Octop package release
• Updating version numbers across release files
• Drafting a Chinese changelog from commits

Deploy ClawHub to production or publish a stable CLI release to npm. Check prerequisites for the exact commit, run the release workflow, and verify the deployed behavior or published version with traceable release evidence.

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

• Deploy ClawHub to production
• Publish a stable ClawHub CLI version
• Check release prerequisites for a specific commit

Review release notes stored in changeset files before a release. Check that entries describe user-facing changes, group related updates, remove unnecessary implementation details, and commit the resulting edits.

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

• Reviewing changeset files before a release
• Grouping related changes into one release note
• Rewriting technical notes for users

Prepare a finished game mod for release by checking packaged files, arranging the required folder structure, writing installation instructions and credits, and drafting a video-led announcement. Includes versioning and platform-specific packaging guidance for user-controlled publishing.

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

• Checking a mod package before release
• Packaging a mod for its distribution platform
• Writing installation instructions and credits

Check a Proofpack release candidate before packaging by running tests, validating the candidate, and inspecting the package locally. Compare the source state and command results with the evidence log, then report passed, failed, or unknown checks.

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

• Checking a Proofpack candidate before packaging
• Comparing local verification with recorded evidence
• Finding unverified checks or uncovered changes

Guide gh-aw release preparation and assess whether command-line changes break existing usage. The reference covers changesets, which record release changes, version previews, release steps, firewall log classification, and summaries of Go module usage.

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

• Preview a release version and changelog
• Assess command-line compatibility and changeset types
• Interpret allowed and blocked traffic in firewall logs

Prepare and validate a version update for @macro-inc/sdk, then track its automatic release after an authorized merge. Verify the published version and npm distribution label, and report whether the release is prepared, publishing, failed, or published.

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

• Preparing an SDK version update
• Validating package contents before release
• Checking automatic publication after a merge

Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an existing Observal deployment.

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

Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new version. For changelog-only tasks, use /changelog instead.

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

Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.

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