Bump tar and ng-packagr in /samples/client/petstore/typescript-angular-v4/npm#14
Open
dependabot[bot] wants to merge 1 commit into
Conversation
Removes [tar](https://github.com/isaacs/node-tar). It's no longer used after updating ancestor dependency [ng-packagr](https://github.com/ng-packagr/ng-packagr). These dependencies need to be updated together. Removes `tar` Updates `ng-packagr` from 1.7.0 to 22.0.0 - [Release notes](https://github.com/ng-packagr/ng-packagr/releases) - [Changelog](https://github.com/ng-packagr/ng-packagr/blob/main/CHANGELOG.md) - [Commits](ng-packagr/ng-packagr@v1.7.0...22.0.0) --- updated-dependencies: - dependency-name: tar dependency-version: dependency-type: indirect - dependency-name: ng-packagr dependency-version: 22.0.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
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.
Removes tar. It's no longer used after updating ancestor dependency ng-packagr. These dependencies need to be updated together.
Removes
tarUpdates
ng-packagrfrom 1.7.0 to 22.0.0Release notes
Sourced from ng-packagr's releases.
... (truncated)
Changelog
Sourced from ng-packagr's changelog.
... (truncated)
Commits
e918dc3release: cut 22.0.07f8a814build: update@angular/compiler-clipeer dependency range to support version ...e7d8e38fix(ng-packagr): invalidate angularDiagnosticCache for html changes7204d85build: update pnpm workspace configuration and remove redundant pnpm settings2684271build: lock file maintenance15a0f56build: update dependency node to v245827827build: update@angular/ng-devdigest to a450a243439543build: update pnpm to v11.4.0efed766build: update dessant/lock-threads digest to 89ae32b27ae92ebuild: update all non-major dependencies to v8.60.0Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for ng-packagr since your current version.
Dependabot 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.