hotfix-release
Create a hotfix release branch, cherry-pick commits, bump the version, and open a draft PR. Use when: hotfix, patch release, cherry-pick to release, hotfix nuget, hotfix npm, release branch fix, backport fix.
- License 许可
- MIT
- 所属仓库
- microsoft/rayfin
- 最近更新
- 2026-11-12
- Stars
- ★ 662
- Forks
- 77
01 前言 Front Matter
- name
- hotfix-release
- license
- MIT
- metadata
- { "author": "rayfin", "version": "1.0" }
- description
- Create a hotfix release branch, cherry-pick commits, bump the version, and open a draft PR. Use when: hotfix, patch release, cherry-pick to release, hotfix nuget, hotfix npm, release branch fix, backport fix.
03 SKILL.md 正文
Create a hotfix release for a previously published NuGet or npm package.
Input: The user provides:
- Package type:
nugetornpm - Version to patch: The published version to hotfix (e.g.,
0.0.45for NuGet,1.31.0for npm) - Commits to cherry-pick: One or more commit SHAs, PR numbers, or branch names containing the fix
If any input is missing, use the AskUserQuestion tool to collect it:
- If package type is unclear, ask:
nugetornpm? - If version is missing, list recent tags with
git tag -l "nuget/v*" --sort=-version:refname | head -10(ornpm/v*) and let the user pick - If commits are missing, ask for the commit SHAs or PR numbers to cherry-pick
Steps
1. Validate the tag exists
git fetch origin --tags
git rev-parse "{{type}}/v{{version}}" >/dev/null 2>&1
If the tag doesn't exist, stop and tell the user. List available tags for that package type to help them.
2. Determine the hotfix version
NuGet: Use 4-part versioning. Check for existing hotfix tags:
git tag -l "nuget/v{{version}}.*" --sort=-version:refname
- If no prior hotfix: new version is
{{version}}.1 - If
{{version}}.Nexists: new version is{{version}}.N+1
npm: Use semver patch bump. Parse the version parts and increment patch:
1.31.0→1.31.1- If
npm/v1.31.1exists, use1.31.2, etc.
Announce the computed hotfix version to the user before proceeding.
3. Create the release branch
git checkout -b release/{{type}}-v{{version}} {{type}}/v{{version}}
git push origin release/{{type}}-v{{version}}
4. Create the fix branch and cherry-pick
git checkout -b fix/hotfix-{{type}}-v{{hotfix_version}} release/{{type}}-v{{version}}
Cherry-pick each provided commit:
git cherry-pick {{commit_sha}}
If a cherry-pick conflicts:
- Show the conflicting files to the user
- Ask them to resolve
- After resolution, run
git cherry-pick --continue
5. Bump the version
NuGet: Edit packages/host/Version.props — set <VersionPrefix> to the hotfix version:
<VersionPrefix>{{hotfix_version}}</VersionPrefix>
npm: Edit packages/typescript-sdk/core/package.json and any other affected packages — set "version" to the hotfix version. Rush version policies apply to all packages in the typescript-sdk policy, so update each affected package.
6. Commit the version bump
git add -A
git commit -m "chore(host): bump {{type}} version to {{hotfix_version}} for hotfix" --no-verify
7. Push and create a draft PR
git push origin fix/hotfix-{{type}}-v{{hotfix_version}}
Create a draft PR targeting release/{{type}}-v{{version}} (not main):
- Title:
fix({{type}}): hotfix v{{hotfix_version}} - Body: List the cherry-picked commits and the version bump
- Draft: true
8. Summary
After creating the PR, print a summary:
✅ Hotfix prepared
Package type: {{type}}
Base version: {{version}}
Hotfix version: {{hotfix_version}}
Release branch: release/{{type}}-v{{version}}
Fix branch: fix/hotfix-{{type}}-v{{hotfix_version}}
PR: {{pr_url}}
Next steps:
1. Review and merge the PR
2. Queue the rayfin.official pipeline on release/{{type}}-v{{version}}
- Set Publish{{Type}}: true
3. Pipeline will publish and tag {{type}}/v{{hotfix_version}}
Error Handling
- Tag not found: List available tags and ask the user to pick the correct version
- Cherry-pick conflict: Show conflicting files, let the user resolve, then continue
- Branch already exists: Ask the user if they want to use the existing branch or create a new one
- Version already tagged: Increment to the next available revision and confirm with the user
04 同仓库更多 Skills
rayfin-getting-started
Use when starting or creating a NEW Rayfin app, or when a Rayfin task comes up and you are not yet inside a Rayfin project. Gets you into a project with the Rayfin CLI, then hands off to the authoritative, version-locked in-project rayfin skill/docs that own all in-project work. Triggers: build a Rayfin app, start a Rayfin project, create a new Rayfin app, create-rayfin, npm create @microsoft/rayfin, rayfin init, scaffold rayfin, rayfin CLI, rayfin template, universal app, awesome-rayfin gallery, get started with Rayfin
visuals
Use when user wants to incorporate charts, graphs, data grid, or other visual representations of data into their project. Use VegaVisual and DataGrid components to create these visuals, utilizing the shared DataTable input, formatting, theme, and interactivity. Covers the onInteraction selection/click events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections. Triggers: chart, graph, plot, dashboard, KPI, metric, trend, scorecard, data grid, visualize.
schema-discovery
Explore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.
query-design
Separates DAX data-fetching from TypeScript presentation. Guides when to use DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS, BLANK handling, filtering, multi-grain queries, cross-filtering and cross-highlight subset/overlay queries, and format strings.
functions-capability
Apply and build the Universal App functions capability. Use for trusted server-side logic, secrets, external APIs, custom model endpoints, published Fabric data agents, webhooks, or privileged operations.
fabric-sdk
How to query Fabric data from a running app through the Rayfin connectors client. Use getRayfinClient().connectors.<name>.executeQuery to run DAX against a semantic model, and toQueryResult to normalize the response.