Reformat package.json before publishing

[kibertoad]

Summary by CodeRabbit

• Chores
  • Updated the release publishing workflow with additional formatting validation checks before deployment
  • Enhanced version control process with explicit commit and tag creation during releases
  • Improved release automation by separating Git operations into dedicated workflow steps
  • Reformatted package metadata configuration for consistency

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The GitHub Actions publish workflow is enhanced with explicit formatting and Git operations. A lint:fix step is added after version bumping, followed by Git commit, tag creation, and push operations instead of relying on npm for these tasks. The package.json file's "files" field is reformatted to a single line without semantic changes.

Changes

Cohort / File(s)	Change Summary
CI/CD Workflow .github/workflows/publish.yml	Adds "Fix formatting" step to run lint:fix and "Commit and push" step to explicitly stage changes, commit with version message, create version tag, and push commits and tags to repository. Preserves existing "Bump version" step with --no-git-tag-version flag.
Package Configuration package.json	Reformats "files" array property from multi-line to single-line layout; no changes to values or semantics.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• .github/workflows/publish.yml: Verify that the explicit Git operations (commit message format, tag naming) align with intended versioning strategy and that --no-git-tag-version prevents double-tagging.
• package.json: Trivial formatting change; confirm no unintended whitespace modifications.

Poem

🐰 A workflow refined with a lint and a push,
No more npm magic—just Git in a rush!
Files neatly formatted, one line so clean,
The prettiest pipeline we've ever seen! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/reformat

---

📜 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 f7be8ba and f12cded.

📒 Files selected for processing (2)

• .github/workflows/publish.yml (1 hunks)
• package.json (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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