bump-sentry-dependency
/bump-sentry-dependency
Bumps an existing Python dependency in getsentry/sentry through the repository's self-serve GitHub Actions workflow. Use when asked to update, upgrade, or bump a Python package version in Sentry. Does not apply to new dependencies, JavaScript packages, or informational questions about dependency management.
- Author
- getsentry ↗
- Repository
- sentry ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Bumps an existing Python dependency in getsentry/sentry through the repository's self-serve GitHub Actions workflow. Use when asked to update, upgrade, or bump a Python package version in Sentry. Does not apply to new dependencies, JavaScript packages, or informational questions about dependency management.
Original author description
Bumps an existing Python dependency in getsentry/sentry through the repository's self-serve GitHub Actions workflow. Use when asked to update, upgrade, or bump a Python package version in Sentry. Does not apply to new dependencies, JavaScript packages, or informational questions about dependency management.
How it works
- Preflight without side effects
- Require confirmation
- Dispatch and report
- Handle failures narrowly
SKILL.md preview
--- name: bump-sentry-dependency description: Bumps an existing Python dependency in getsentry/sentry through the repository's self-serve GitHub Actions workflow. Use when asked to update, upgrade, or bump a Python package version in Sentry. Does not apply to new dependencies, JavaScript packages, or informational questions about dependency management. --- # Bump a Sentry Python Dependency For an existing Python dependency, prefer `.github/workflows/bump-version.yml` over editing `pyproject.toml` and `uv.lock` locally. The workflow creates a non-draft PR when it produces a diff; it does not approve or merge the PR. Do not use this workflow for new dependencies, JavaScript packages, other repositories, or informational questions. ## Preflight without side effects Before asking for confirmation: 1. Confirm the package is in `[project].dependencies` or the `dev` dependency group in `pyproject.toml`. 2. Resolve the exact target version. If the user says `latest`, determine the intended stable version first. 3. Check for an existing PR from `bot/bump-version/<package>/<version>`. Reuse and report it instead of dispatching a duplicate. ## Require confirmation Dispatching the workflow is an external side effect: it starts a GitHub Actions job and normally opens a PR. A request such as "bump package X" is not by itself explicit approval for those effects. Unless the user already said to run the workflow or open the PR, ask and wait: > This will dispatch Sentry's `bump-version` workflow and open a PR if it > produces a change. Would you like me to run it? Do not treat approval for this dispatch as approval to modify `getsentry/pypi`, approve the PR, enable auto-merge, or merge it. ## Dispatch and report After approval, run: ```bash gh workflow run bump-version.yml \ --repo getsentry/sentry \ --field package=<package> \ --field version=<version> ``` Omit `pr_options` unless the user explicitly requested it. Use the run URL/ID returned by `gh workflow run` to monitor that exact run: ```bash gh run watch <run-id> --repo getsentry/sentry --exit-status ``` GitHub can occasionally return no run details. Only then fall back to `gh run list`, filtered by this workflow, `workflow_dispatch`, the authenticated user, and the dispatch time. If the run succeeds, find the PR by its bot branch. Verify that changed files are limited to `pyproject.toml` and `uv.lock` and that the dependency changes are expected, then report the run URL, PR URL, current CI state, and review state. Do not wait indefinitely for human review. Never describe the dependency as landed until the PR is merged. If the run succeeds without a PR, inspect its log. No diff usually means the repository already satisfies the requested version. ## Handle failures narrowly ```bash gh run view <run-id> --repo getsentry/sentry --log-failed ``` The workflow retries resolver failures for roughly 20 minutes. After it fails, distinguish a genuinely missing internal-PyPI release from a dependency conflict. A mirror PR will not fix an incompatible dependency set. Changing `getsentry/pypi` is a separate external side effect. Explain why it is needed and get separate explicit approval before making that cross-repository change.
Files in this package (3)
- SKILL.md 3 KB
- SOURCES.md 2 KB
- SPEC.md 3 KB
Versions
The database has no other skills named bump-sentry-dependency.
Database snapshot: 13.11.2026 · package version 2d196629ed9b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sentry-sdk-upgrade
Upgrade the Sentry JavaScript SDK across major versions. Use when asked to upgrade Sentry, migrate to a newer version, fix deprecated Sentry APIs, or resolve breaking changes after a Sentry version bump. - 95bump-conventions
Bump the @sentry/conventions dependency to a new version across every package in the monorepo. Use when upgrading, bumping, or aligning @sentry/conventions, or when a new @sentry/conventions release needs to be pulled into all workspaces. - 95upgrade-dep
Upgrade a dependency in the Sentry JavaScript SDK. Use when upgrading packages, bumping versions, or fixing security vulnerabilities via dependency updates. - 100deps-upgrade
Upgrade dependencies with breaking change detection and migration planning. Use when asked to "upgrade dependencies", "update packages", "bump dependencies", "bump <package> to <version>", "update <package> to version <version>", "handle dependabot PR", "handle renovate PR",… - 100fix-sentry-issues
使用 Sentry MCP 发现、分类并根因修复生产问题。用于修复 Sentry 问题、分类生产错误、排查错误尖峰或清理 Sentry 噪声。需要 Sentry MCP 服务。 - 90dependency-update-review
Review dependency updates, package manager changes, lockfile diffs, version bumps, and dependency risk. Use when the user asks whether dependency updates are safe, wants to upgrade packages, or needs a dependency PR reviewed.