release

Automate Sentry JavaScript SDK release preparation with versioning and changelog updates.

8.7k|1.8k|Updated Feb 1, 2012
One-click install
npx skills add https://github.com/getsentry/sentry-javascript --skill release-getsentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/getsentry/sentry-javascript/tree/main/.agents/skills/release
Command: npx skills add https://github.com/getsentry/sentry-javascript --skill release-getsentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of preparing and publishing new releases for the Sentry JavaScript SDK, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Release Preparation: Guides users through creating release branches, updating changelogs, and committing changes.
  • Version Management: Assists in determining and applying semantic versioning.
  • First-time SDK Releases: Provides a checklist for onboarding new SDKs into the release process.
  • Use Case: When a new version of the Sentry JavaScript SDK is ready, this Skill helps automate the steps to create the release branch, update the changelog, and prepare for publishing.

Quick Start

Use the release skill to prepare a new release for version 7.10.0.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a new Sentry JavaScript SDK release?

To publish a new Sentry JavaScript SDK release, you automate the process by creating release branches, managing versioning, and updating changelogs. This ensures consistency and adherence to best practices during release preparation.

What is the process for preparing a first-time Sentry SDK release?

Preparing a first-time Sentry SDK release involves following a specific checklist for onboarding new SDKs into the release process. This requires strict adherence to semantic versioning and specific documentation guidelines.

How do I manage versioning and changelog updates for a Sentry SDK?

Managing versioning and changelog updates for a Sentry SDK involves applying semantic versioning rules and committing changelog modifications. The process automates these updates alongside release branch creation.

Do I need to follow semantic versioning when publishing a Sentry SDK?

Yes, you need to follow semantic versioning when publishing a Sentry SDK. Adherence to semver is a strict requirement for managing version updates and ensuring consistency across new SDK releases.

What documentation guidelines are required for onboarding new Sentry SDKs?

Onboarding new Sentry SDKs requires adherence to specific documentation guidelines alongside the standard release process. This ensures new SDKs are properly integrated before versioning and changelog updates begin.