build: update patch-package patch file - #1051
Merged
ericcrosson-bitgo merged 1 commit intoJul 28, 2025
Merged
Conversation
ericcrosson-bitgo
marked this pull request as ready for review
July 27, 2025 17:28
ericcrosson-bitgo
enabled auto-merge
July 27, 2025 17:28
The motivation behind this commit is to reduce the amount of
noise currently printed by `npm install` in the root of this
repository. Installing npm dependencies currently prints the following:
```
$ npm ci
> @api-ts/base@0.1.0 postinstall
> patch-package
patch-package 8.0.0
Applying patches...
@semantic-release/npm@10.0.5 ✔
Warning: patch-package detected a patch file version mismatch
Don't worry! This is probably fine. The patch was still applied
successfully. Here's the deets:
Patch file created for
@semantic-release/npm@10.0.5
applied to
@semantic-release/npm@12.0.1
At path
node_modules/@semantic-release/npm
This warning is just to give you a heads-up. There is a small chance of
breakage even though the patch was applied successfully. Make sure the package
still behaves like you expect (you wrote tests, right?) and then run
patch-package @semantic-release/npm
to update the version in the patch file name and make this warning go away.
```
It looks like we created a patch for version
@semantic-release/npm@10.0.5, and have since updated (probably through
Dependabot) to @semantic-release/npm@12.0.1.
The underlying dependency doesn't seem to have changed in a way that
invalidates our patch, so I followed patch-package's instruction
and ran:
```sh
node_modules/.bin/patch-package @semantic-release/npm
```
This commit adds the generated file to version control. It also removes
the patch configured to run on @semantic-release/npm@10.0.5, since that
version is no longer installed in this repository (and removing this file
is necessary to silence the patch-package warning).
Update: and then I moved the comment over... you know, I could have just
renamed the file!
ericcrosson-bitgo
force-pushed
the
build-update-patch-package-patch-file
branch
from
July 27, 2025 17:31
2cf662e to
83435c9
Compare
bitgopatmcl
approved these changes
Jul 28, 2025
|
🎉 This PR is included in version @api-ts/openapi-generator@5.8.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@2.0.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/express-wrapper@2.0.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The motivation behind this commit is to reduce the amount of
noise currently printed by
npm installin the root of thisrepository. Installing npm dependencies currently prints the following:
It looks like we created a patch for version
@semantic-release/npm@10.0.5, and have since updated (probably through
Dependabot) to @semantic-release/npm@12.0.1.
The underlying dependency doesn't seem to have changed in a way that
invalidates our patch, so I followed patch-package's instruction
and ran:
This commit adds the generated file to version control. It also removes
the patch configured to run on @semantic-release/npm@10.0.5, since that
version is no longer installed in this repository (and removing this file
is necessary to silence the patch-package warning).