Skip to content

Fix npm release config being in the wrong place#14

Merged
boliveira merged 1 commit into
masterfrom
support/fix-wrong-place-npm
May 25, 2026
Merged

Fix npm release config being in the wrong place#14
boliveira merged 1 commit into
masterfrom
support/fix-wrong-place-npm

Conversation

@satazor
Copy link
Copy Markdown
Contributor

@satazor satazor commented May 25, 2026

No description provided.

Copilot AI review requested due to automatic review settings May 25, 2026 14:10
@boliveira boliveira merged commit c02a67f into master May 25, 2026
6 of 8 checks passed
@boliveira boliveira deleted the support/fix-wrong-place-npm branch May 25, 2026 14:10
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Moves the release-it npm publishing configuration out of package.json and into .release-it.json, aligning the npm settings with where release-it actually reads its configuration.

Changes:

  • Removed the top-level "npm" config block from package.json.
  • Added the "npm": { "publish": true, "skipChecks": true } block to .release-it.json for release-it to consume.

Reviewed changes

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

File Description
package.json Removes misplaced npm release configuration from the package manifest.
.release-it.json Adds the release-it npm publish configuration in the correct config file.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants