Skip to content

ci(.github/workflows/release): change changesets commit type from 'ci' to 'chore' #9732

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ci(.github/workflows/release): change changesets commit type from 'ci' to 'chore' #9732

wants to merge 1 commit into from
+2 −2

Conversation

sukvvon
Copy link
Contributor

@sukvvon sukvvon commented Oct 6, 2025 •
edited by coderabbitai bot
Loading

🎯 Changes

Changes the commit type for automated version updates from ci to chore.

Package version updates are not CI/CD configuration changes, but rather maintenance tasks related to the build/release process. According to conventional commits standards, chore is more semantically appropriate for version bumps.

✅ Checklist

  • I have followed the steps in the Contributing guide.
  • I have tested this code locally with pnpm test:pr.

🚀 Release Impact

  • This change affects published code, and I have generated a changeset.
  • This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

  • Chores
    • Standardized automated release commit and PR titles to “chore: version packages” for clearer history.
    • Improves readability across release notes and repository activity.
    • No changes to features, performance, builds, or deployment logic; workflow behavior remains the same.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Oct 6, 2025

⚠️ No Changeset found

Latest commit: b1d6dce

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 6, 2025 •
edited
Loading

Walkthrough

Updated the Changesets step in .github/workflows/release.yml to use “chore: version packages” for both the commit message and PR title, replacing “ci: Version Packages.” No logic, steps, or control flow were changed.

Changes

Cohort / File(s) Summary
Release workflow messaging
.github/workflows/release.yml		 Updated Run Changesets (version or publish) step commit and title values from "ci: Version Packages" to "chore: version packages".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

a hop and a tag, I nudge the prose,
from “ci” to “chore,” the message grows.
carrots align, releases sing,
tidy labels on every thing.
thump-thump—versioned packages go! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed The title clearly summarizes the main change by stating the shift of the Changesets commit type from “ci” to “chore” and references the specific workflow file where this update occurs, making it concise, specific, and directly aligned with the changes in the pull request.
Description Check ✅ Passed The description adheres to the repository’s template by including a detailed 🎯 Changes section with motivation, a completed ✅ Checklist, and a correctly marked 🚀 Release Impact indicating this is a docs/CI/dev-only change, providing all required information in the specified structure.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f82d8e and b1d6dce.

📒 Files selected for processing (1)
  • .github/workflows/release.yml (1 hunks)
🔇 Additional comments (1)
.github/workflows/release.yml (1)

57-58: Commit message type update looks good

The switch to chore better matches conventional commit semantics for maintenance/version bumps, and the lowercase subject keeps things consistent. 👍

Comment @coderabbitai help to get the list of available commands and usage tips.

@nx-cloud Nx Cloud
Copy link

nx-cloud bot commented Oct 6, 2025 •
edited
Loading

View your CI Pipeline Execution ↗ for commit b1d6dce

Command Status Duration Result
nx affected --targets=test:sherif,test:knip,tes... ✅ Succeeded 46s View ↗
nx run-many --target=build --exclude=examples/*... ✅ Succeeded 1s View ↗

☁️ Nx Cloud last updated this comment at 2025-10-06 11:41:27 UTC

@pkg-pr-new pkg.pr.new
Copy link

pkg-pr-new bot commented Oct 6, 2025

More templates

@tanstack/angular-query-experimental

npm i https://pkg.pr.new/@tanstack/angular-query-experimental@9732

@tanstack/eslint-plugin-query

npm i https://pkg.pr.new/@tanstack/eslint-plugin-query@9732

@tanstack/query-async-storage-persister

npm i https://pkg.pr.new/@tanstack/query-async-storage-persister@9732

@tanstack/query-broadcast-client-experimental

npm i https://pkg.pr.new/@tanstack/query-broadcast-client-experimental@9732

@tanstack/query-core

npm i https://pkg.pr.new/@tanstack/query-core@9732

@tanstack/query-devtools

npm i https://pkg.pr.new/@tanstack/query-devtools@9732

@tanstack/query-persist-client-core

npm i https://pkg.pr.new/@tanstack/query-persist-client-core@9732

@tanstack/query-sync-storage-persister

npm i https://pkg.pr.new/@tanstack/query-sync-storage-persister@9732

@tanstack/react-query

npm i https://pkg.pr.new/@tanstack/react-query@9732

@tanstack/react-query-devtools

npm i https://pkg.pr.new/@tanstack/react-query-devtools@9732

@tanstack/react-query-next-experimental

npm i https://pkg.pr.new/@tanstack/react-query-next-experimental@9732

@tanstack/react-query-persist-client

npm i https://pkg.pr.new/@tanstack/react-query-persist-client@9732

@tanstack/solid-query

npm i https://pkg.pr.new/@tanstack/solid-query@9732

@tanstack/solid-query-devtools

npm i https://pkg.pr.new/@tanstack/solid-query-devtools@9732

@tanstack/solid-query-persist-client

npm i https://pkg.pr.new/@tanstack/solid-query-persist-client@9732

@tanstack/svelte-query

npm i https://pkg.pr.new/@tanstack/svelte-query@9732

@tanstack/svelte-query-devtools

npm i https://pkg.pr.new/@tanstack/svelte-query-devtools@9732

@tanstack/svelte-query-persist-client

npm i https://pkg.pr.new/@tanstack/svelte-query-persist-client@9732

@tanstack/vue-query

npm i https://pkg.pr.new/@tanstack/vue-query@9732

@tanstack/vue-query-devtools

npm i https://pkg.pr.new/@tanstack/vue-query-devtools@9732

commit: b1d6dce

@sukvvon sukvvon marked this pull request as ready for review October 6, 2025 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@sukvvon