Results for “version”

npm package maintenance and lifecycle management for monorepo extensions. Covers health audits, dependency sync, version bumping, changelog updates, pre-publish checks, coordinated publishing, and post-publish verification. **Triggers — use this skill when:** - User asks to "publish", "release", or "version bump" extensions/packages - User says "audit packages", "check package health", "dependency sync" - User asks to "update changelogs", "prepare release", "pre-publish check" - User mentions "npm publish", "version management", "package lifecycle" - User wants to "sync dependencies" or "align versions" across packages - User asks "what needs publishing" or "which packages changed" **Covers:** Monorepo with multiple npm packages under `extensions/`. Each package has its own package.json, CHANGELOG.md, README.md, and version. Packages are scoped (e.g. `@e9n/pi-*`) and published individually.

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

Cuts the next release of the unified Prisma CLI: bumps the root package.json version (on the Prisma 8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every lockstep workspace package, and opens a PR titled "chore(release): bump to <next-version>". When the maintainer merges the PR, the `Publish to npm` workflow ships @prisma/cli-engine and @prisma/cli under dist-tag `latest` (RC versions get a pre-release GitHub Release). Use when a maintainer asks to "cut the next RC", "cut the next release", "bump to the next version", "open a release PR", or "prepare a publish PR".

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

Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.

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

Automate version bumping following semantic versioning and changelog management. Use when the user wants to bump a version, create a release, update the changelog, or tag a new version in a project using semver conventions and Keep a Changelog format.

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

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

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

Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.

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

Add released versions of Apache SkyWalking AI Sessionizer to its Homebrew tap, Formula/ on main in apache/skywalking-ai-sessionizer. Writes asz@VERSION from the voted packages, moves asz to the newest version, checks every formula with brew, and opens a pull request to main in this repository. Use after a version is published, or to add older released versions.

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

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

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

Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the `changelog` skill calls for a release.

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

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

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

Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.

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

Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.

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

Hunt shadow / zombie / undocumented API surface (OWASP API9 Improper Inventory Management) — enumerate the full API version history (v1/v2/beta/legacy paths, header- and subdomain-based versioning), pull and diff every reachable OpenAPI/Swagger spec (including ones only findable via the Wayback Machine), and behaviorally diff old vs. current versions for auth/rate-limit/validation regressions rather than just response-shape differences. Distinct from hunt-api-misconfig, which owns exploitation once you have a spec or endpoint (mass assignment, JWT, OData, Swagger-chain attacks); distinct from hunt-subdomain, which owns host-level discovery. This skill owns the version-inventory and behavioral-diff workflow itself. Use when the target has versioned API paths, multiple specs, a changelog referencing deprecated endpoints, or a mobile app whose hardcoded backend calls look older than the current web app's.

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

Design and review REST APIs with consistent URLs, HTTP status codes, error responses, and pagination, which divides results into smaller batches. Covers authentication, access limits, and versioning to help define clear behavior for API users.

• Designing endpoints for a new REST API
• Reviewing status codes and error responses
• Choosing pagination for list endpoints

Design and review REST APIs with consistent resource names, HTTP status codes, error responses, and pagination, which splits lists into smaller results. It also guides filtering, authentication, request limits, and versioning for public or internal APIs.

• Designing URLs and responses for a new API
• Reviewing an existing API specification
• Choosing pagination and filtering methods

Publish static websites and built web apps to GitHub Pages, Cloudflare Pages, or Netlify. The workflow includes preview approval, git-tagged deployment versions, live URL checks, and restoring an earlier version when an update needs reversing.

• Publish a portfolio or documentation site
• Share a dashboard or prototype through a public URL
• Update an existing site with a recorded deployment version

Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.

• Split mixed changes into focused commits
• Prepare branches and pull requests for review
• Separate parallel work with git worktrees

Prepare Ant Design releases by checking branches, version numbers, and existing changelogs, then creating a release pull request. After it is merged, the skill can run npm publish when explicitly requested.

• Prepare a release pull request
• Choose a patch or minor version increment
• Check version numbers against English and Chinese changelogs

Organize software releases on GitHub, from version suggestions and release notes to testing, builds, and deployment. Coordinate multiple packages or repositories, roll changes out in stages, and configure rollback to restore an earlier release when problems occur.

• Preparing version updates and release notes
• Coordinating releases across packages and repositories
• Deploying in stages with monitoring and rollback

Update all Storybook packages in a project to a chosen release or canary, an early development build. Use it to test changes in external apps, reproduce bugs, and keep package versions aligned while handling peer dependencies.

• Test a canary build in an external app
• Reproduce a bug with a specific Storybook release
• Update all Storybook packages to the latest stable release

Manage Contentful spaces, the containers used to organize content, from Claude Code through Composio. List accessible spaces, inspect creation dates and current versions, rename spaces, and review the organization's space inventory.

• List all accessible Contentful spaces
• Check a space's metadata and current version
• Rename a Contentful space

Benchmark how CodeGraph affects an agent investigating a real codebase. Choose a version, language, repository, and execution mode, then compare cost, tool calls, file reads, and answer correctness with and without CodeGraph.

• Evaluating a local development build
• Auditing a published CodeGraph version
• Comparing investigation cost and file reads

Create a substantial technical manual for one exact system version. Organize authoritative sources, record offline inputs and outputs, explain behavior with figures, and audit the text and supporting evidence for consistency.

• Documenting a protocol or file format at a fixed version
• Building reproducible offline request and response records
• Adding a section with figures and traceable sources

Update the published Remotion plugin for Codex and ChatGPT to a released version. Prepare and validate an upload ZIP, preserve existing listing details, and follow the dashboard workflow through review and publication verification.

• Update the public plugin to a released Remotion version
• Prepare an upload ZIP while preserving listing details
• Resume an existing draft or review