'release' 검색 결과

Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.

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

• Preparing a new version from recent changes
• Updating changelogs in multiple languages
• Previewing release changes without modifying files

Prepare an Apache bRPC release with tracked progress, version updates, release candidate checks, and draft release notes and emails. The workflow leaves signing, publishing, and other external release actions to the release manager.

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

• Prepare version files and a release branch
• Resume release work from a saved progress record
• Verify local or uploaded release packages

Use when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release', 'release update settings metadata', 'FlowSettings release update field', 'release run sheet', 'preview sandbox refresh freeze', 'settings deploy flipped a release update'. Also covers: which Release Updates are deployable as Settings metadata, the release run sheet artefact, and the preview opt-in refresh-date rule. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.

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

Prepare a software release from the dev branch by turning commits into a changelog, updating the version, and creating a pull request to main. The workflow also covers release tags, branch synchronization, and Homebrew package updates.

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

• Preparing a patch, minor, or major release
• Turning changes into a user-facing changelog
• Updating Homebrew packages after publishing binaries

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

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

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.

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

• Preparing the next Prisma 8 release candidate
• Updating versions across workspace packages
• Assembling upgrade guides and release notes

Check release readiness inside the herdr repository by comparing changes since the base release with upcoming release notes and documentation. Review CLI descriptions, issue references, checks, and benchmarks, then report readiness.

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

• Check release notes against changes since the base release
• Review upcoming documentation before a release
• Inspect issue references that release CI will close

Prepare a stable Paseo release by following the documented release flow and completion checklist. Use it for a fresh patch or minor release, or to promote a beta version to stable.

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

• Release a new stable patch version of Paseo
• Release a new stable minor version of Paseo
• Promote a Paseo beta version to stable

Polish a published qiankun GitHub Release into readable English and Simplified Chinese notes. The skill clarifies changes, removes repeated entries, preserves package versions and PR references, and updates the release after approval.

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

• Polishing the latest published qiankun release notes
• Removing repeated changes across package sections
• Preparing matching English and Simplified Chinese release notes

Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.

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

• Checking published development artifacts before release
• Testing changes to the Release Canary workflow
• Investigating installation or sandbox test failures

Manage OpenSpec releases by auditing merged changes and release records, checking release pull requests, and verifying publication. Support stable and beta releases, resume from the current GitHub state, and finish with polished release notes.

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

• Checking release readiness and missing change records
• Preparing a pull request for missing release records
• Resuming a release after human approval

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 a beta release of Paseo by following the project's release documentation. The skill directs the agent through the beta workflow and its completion checklist, keeping the task tied to the documented process.

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

• Preparing a Paseo beta release
• Following the documented beta release workflow
• Working through the beta release completion checklist

Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.

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

REA의 Git 이력을 특정 버전으로 고정해 변경 이력과 릴리스 노트를 정리합니다. 기여자 감사 표기를 검증하고 Release Please의 공개 본문과 일치하는지 확인합니다.

• Git 이력으로 릴리스 노트 작성
• 사용자에게 미치는 변경 영향 정리
• 기여자 감사 표기와 이슈 링크 확인

Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.

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

• Coordinating a complete Paperclip release
• Promoting a tested canary to a stable release
• Checking release candidates with Docker smoke tests

Prepare and guide software releases using rules discovered in the project and its automated build workflows. It tracks version files, helps draft release notes, runs release steps with confirmation, and checks the published result.

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

• Preparing a software version release
• Updating version numbers across multiple files
• Drafting release notes from commit history

Guide a Kortix production release from choosing a version and writing release notes to testing on staging, merging the release pull request, and verifying production. Diagnose blocked promotions and direct fixes back to the dev branch.

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

• Choose a version number for a Kortix release
• Promote dev through staging to production
• Investigate a blocked release

Promote the latest qualified OpenShell prerelease to a stable release after maintainer approval. Check that qualification matches the tag and commit, present changes since the previous stable version, and monitor the release workflow through completion.

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

• Choosing a qualified prerelease for stable promotion
• Reviewing changes since the previous stable release
• Creating and qualifying a missing prerelease

Prepare an Ant Design Mobile package release by checking the version, build, and package contents. After the user publishes to npm manually, verify the published package and create its Git tag and bilingual GitHub Release.

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

• Prepare an Ant Design Mobile release
• Check files included in an npm package
• Draft release notes in Chinese and English

Prepare and publish a Plannotator release with contributor credits, coordinated version updates, ordered builds, and tag-triggered publishing. The workflow also checks package contents, security scan results, and evidence showing how release files were built.

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

• Draft release notes with contributor credits
• Update versions consistently across package files
• Check builds and package contents before release

Build beta versions of the Composio CLI, promote a tested beta to a stable release, and investigate failed releases. Guides verification of published binaries and installation tests through the Build CLI Binaries workflow.

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

• Build a CLI beta release
• Promote a tested beta to stable
• Verify release assets and installation

Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.

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

• Release a specified Symphony version
• Prepare the next patch release
• Tag the merged release commit

Coordinate a game release from candidate preparation through testing, release approval, and deployment. Assign work to role-based agents and collect quality results, patch notes, launch messaging, and a post-release monitoring plan.

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

• Prepare a release candidate and checklist
• Collect testing and release readiness results
• Decide whether a release should proceed