Skip to content

chore: update native loader during releases #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chenjiahan merged 1 commit into from
Aug 10, 2026
Merged

chore: update native loader during releases #282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions .agents/skills/release-rstack/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,14 +19,16 @@ If the version is missing, ask for it before making changes.

3. Create and switch to `release/v<version>` from the clean default-branch HEAD.

4. Update only the `version` field in `packages/rstack/package.json` to `<version>`.
4. Update the `version` field in `packages/rstack/package.json` to `<version>`.

5. Review the diff and confirm it contains exactly the one version-field change above.
5. Run `pnpm --filter rstack build:native` to regenerate `packages/rstack/binding.cjs` and `packages/rstack/binding.d.cts` for the new version. Do not edit generated binding files manually.

6. Create a commit with this exact message: `release: v<version>`.
6. Review the diff and confirm it contains only the version-field change and regenerated binding files above.

7. Push the branch to `origin`. Recheck that the branch being pushed is `release/v<version>` and never push the default branch directly.
7. Create a commit with this exact message: `release: v<version>`.

8. Create a pull request against the default branch. In Codex, use the GitHub connector/plugin; use another available GitHub workflow only when the connector is unavailable. Use `release: v<version>` as the PR title.
8. Push the branch to `origin`. Recheck that the branch being pushed is `release/v<version>` and never push the default branch directly.

9. Create a pull request against the default branch. In Codex, use the GitHub connector/plugin; use another available GitHub workflow only when the connector is unavailable. Use `release: v<version>` as the PR title.

Return the pull request URL.