Add @semantic-release/git to release pipeline

[Copilot]

This updates the release setup to include @semantic-release/git so semantic-release can commit versioned package metadata back to the repository as part of the publish flow.

• Release config

  • Adds an explicit plugins list in release.config.cjs
  • Wires in @semantic-release/git alongside the existing semantic-release stages
  • Configures the git plugin to commit the release-updated package.json

• Dependency update

  • Adds @semantic-release/git as a dev dependency
  • Refreshes pnpm-lock.yaml for the new plugin and its transitive dependencies

• Release commit shape

  • Uses a release commit message that skips CI on the generated version commit

module.exports = {
	branches: ['main', { name: 'next', prerelease: true }],
	plugins: [
		'@semantic-release/commit-analyzer',
		'@semantic-release/release-notes-generator',
		'@semantic-release/npm',
		'@semantic-release/github',
		[
			'@semantic-release/git',
			{
				assets: ['package.json'],
				message: 'chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}',
			},
		],
	],
};

Original prompt

add @semantic-release/git then

[Chronological Review: The conversation began with the user requesting to read a specific document and make changes to the codebase, including branching and modifying files. The user then encountered issues with tests and runtime errors, leading to discussions about skipped tests and size-limit warnings. The user also requested to check PR comments, resolve controversial comments, and interact with GitHub using the CLI. The conversation evolved to include adding badges, discussing scoring metrics, and making further modifications to the README and other documentation files. The most recent commands involved adding a badge to the README, fixing version badges, and adding a package for semantic release.]

[Intent Mapping: The user explicitly requested to read a document, branch from the main, make specific code changes, verify runtime behavior, run tests, open a PR, check test errors, and add badges. They also sought to understand scoring metrics and requested the addition of a code of conduct and contributing guidelines.]

[Technical Inventory: Technologies mentioned include Node.js, bun, deno, and various bundlers like Vite and webpack. The user also referenced tools like size-limit and semantic-release/git. The conversation involved discussions about JSON imports, module resolution, and handling errors in tests.]

[Code Archaeology: Key files discussed include src/accentFolding.js, package.json, and README.md. The user made changes to the README to include badges and requested modifications to the package.json for semantic release.]

[Progress Assessment: The user has completed several tasks, including running tests and verifying runtime behavior. They are in the process of adding documentation and badges, with pending tasks related to creating a branch, committing changes, and opening a PR.]

[Context Validation: All critical information for continuation is captured, including the need to check the current file contents before making edits and the user's ongoing work with GitHub CLI and badge integration.]

[Recent Commands Analysis: The last agent commands executed included:

1. gh api repos/ZRktty/accent-folding/pulls/64/comments/3300377973/replies -X POST -f body="..." - This command was used to post a reply to a PR comment.
2. gh api repos/ZRktty/accent-folding/pulls/64/comments/3300377986/replies -X POST -f body="..." - Another command to post a reply to a different PR comment.
3. The user requested to add a badge to the README and fix the version badge, indicating ongoing work to improve project documentation and visibility.

The immediate pre-summarization state involved the user actively working on adding badges and fixing versioning issues in the README, while also preparing to create a branch and commit changes.]

1. Conversation Overview: - Primary Objectives: The user requested to read a specific document, make code changes, verify runtime behavior, run tests, open a PR, check test errors, and add badges. They also sought to understand scoring metrics and requested the addition of a code of conduct and contributing guidelines. - Session Context: The conversation flowed from initial code modifications to discussions about test errors, badge integration, and documentation improvements. The user engaged with GitHub CLI for PR comments and modifications. - User Intent Evolution: The user's needs evolved from making code changes to enhancing project documentation and understanding project metrics.

2. Technical Foundation:

• Node.js: Version 18 and above for compatibility with certain features.
• bun: A JavaScript runtime used for testing.
• size-limit: A tool for checking bundle sizes.
• semantic-release/git: A package for automating versioning and package publishing.

3. Codebase Status:

• src/accentFolding.js:
  • Purpose: Core functionality for accent folding.
  • Current State: Undergoing modifications for JSON import handling.
• package.json:
  • Purpose: Project metadata and dependencies.
  • Current State: Needs updates for semantic release integration.
• README.md:
  • Purpose: Project documentation.
  • Current State: Updates for badges and versioning.

4. Problem Resolution:

• Issues Encountered: Test failures and runtime errors related to module imports.
• Solutions Implemented: Adjustments to code and documentation, including badge integration.
• Debugging Context: Ongoing troubleshooting of test errors and runtime behavior.

5. Progress Tracking:

• Completed Tasks: Code modifications, test verifications, and badge additions.
• Partially Complete Work: Documentation updates and PR preparations.
• Validated Outcomes: Successful runtime tests with Node.js and bun.

6. Active Work State:

• Current Focus: Adding badges to the README and fixing version badges.
• Recent Context: The user was actively working on integrating badges and preparing for a branch creation and commit.
• Working Code: Modifications to...

Created from VS Code.

[coveralls]

Coverage Report for CI Build 26445628873

Coverage remained the same at 100.0%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	47
Covered Lines:	47
Line Coverage:	100.0%
Relevant Branches:	28
Covered Branches:	28
Branch Coverage:	100.0%
Branches in Coverage %:	Yes
Coverage Strength:	228.38 hits per line

---

💛 - Coveralls

[Copilot]

Pull request overview

This PR updates the project’s semantic-release configuration to include @semantic-release/git, enabling semantic-release to commit the release-updated package.json back to the repository during the release flow.

Changes:

• Define an explicit semantic-release plugins pipeline in release.config.cjs.
• Add and configure @semantic-release/git to commit updated package.json with a CI-skip commit message.
• Add @semantic-release/git to dev dependencies and update pnpm-lock.yaml accordingly.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
release.config.cjs	Adds explicit semantic-release plugin list including @semantic-release/git and its commit settings.
package.json	Adds @semantic-release/git as a dev dependency.
pnpm-lock.yaml	Updates lockfile to include @semantic-release/git and transitive dependency changes.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🎉 This PR is included in version 2.4.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀