chore(deps): bump tmp from 0.2.4 to 0.2.6 in /packages/honkit#519
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps): bump tmp from 0.2.4 to 0.2.6 in /packages/honkit#519dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [tmp](https://github.com/raszi/node-tmp) from 0.2.4 to 0.2.6. - [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md) - [Commits](raszi/node-tmp@v0.2.4...v0.2.6) --- updated-dependencies: - dependency-name: tmp dependency-version: 0.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| "send": "^0.19.2", | ||
| "tiny-lr": "^1.1.1", | ||
| "tmp": "0.2.4" | ||
| "tmp": "0.2.6" |
There was a problem hiding this comment.
🟡 Lockfile not updated to match package.json dependency change
The package.json changes tmp from exact version 0.2.4 to 0.2.6 (pinned, no ^ prefix), but pnpm-lock.yaml was not updated and still references tmp@0.2.4 (specifier: 0.2.4, version: 0.2.4). There is no tmp@0.2.6 entry in the lockfile at all. This means pnpm install --frozen-lockfile will fail due to the mismatch between package.json and the lockfile, and the resolution/integrity information for the new version is missing.
Prompt for agents
The pnpm-lock.yaml file needs to be regenerated to match the updated package.json. Run `pnpm install` at the repository root to update the lockfile, which will: (1) change the specifier for tmp from 0.2.4 to 0.2.6 in the importers section, (2) add a resolution entry for tmp@0.2.6 with its integrity hash, and (3) remove the orphaned tmp@0.2.4 entry if no other package depends on it. Then commit the updated pnpm-lock.yaml alongside the package.json change.
Was this helpful? React with 👍 or 👎 to provide feedback.
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
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.
Bumps tmp from 0.2.4 to 0.2.6.
Commits
41f7159Bump up the versionefa4a06Merge commit from fork7ef2728Check for relative values3d2fe38Bump up the versione162828Merge pull request #309 from fflorent/fix-tmp-dir-with-dirb847d2fFix use of tmp.dir() withdiroptionDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.