Bump the typescript-eslint group with 2 updates #1523
Closed
Conversation
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the typescript-eslint group with 2 updates: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) and [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser). Updates `@typescript-eslint/eslint-plugin` from 8.34.0 to 8.34.1 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.34.1/packages/eslint-plugin) Updates `@typescript-eslint/parser` from 8.34.0 to 8.34.1 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.34.1/packages/parser) --- updated-dependencies: - dependency-name: "@typescript-eslint/eslint-plugin" dependency-version: 8.34.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: typescript-eslint - dependency-name: "@typescript-eslint/parser" dependency-version: 8.34.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: typescript-eslint ... Signed-off-by: dependabot[bot] <[email protected]>
Software Supply Chain Report of ericcornelissen/eslint-plugin-top - 7e0a959 → 1eac975How to read the results 📖Dirty-waters has analyzed your project dependencies and found different categories for each of them:
Total packages in the supply chain: 3🔒 Packages with signature changes ( ❗ Downgraded packages ( 👽 Commits made by both New Authors and Reviewers ( 🙈 Commits approved by New Reviewers ( 😐 Commits made by New Authors ( Fine grained information🐬 For further information about software supply chain smells in your project, take a look at the following tables. ❗ Downgraded packages (
|
| package_name | repo_link | category | old_version | new_version |
|---|---|---|---|---|
@eslint/js |
https://github.com/eslint/eslint | Downgraded package | 9.29.0 | 9.27.0 |
eslint |
https://github.com/eslint/eslint | Downgraded package | 9.29.0 | 9.27.0 |
Call to Action:
👻What do I do now?
For packages with signature changes:
- Why? Changes in code signatures could indicate tampering with the package or compromised build processes, potentially introducing malicious code.
- This means that a dependency either had code signature and now does not, or that the signature was valid and now it's not.
- This could be a security risk, and you should halt the project until you can verify the changes.
For downgraded dependencies:
- Why? Downgrading packages may reintroduce known security vulnerabilities that were fixed in newer versions.
- Check the release notes of the new version to see if the downgrade is intentional. If the new version is more than one release ahead, verify whether any breaking changes in between apply to your project.
- If the downgrade is unintentional, consider updating the package to a version that is compatible with your project.
For commits made by both new authors and reviewers:
- Why? When both authors and reviewers are new to a project, there's a higher risk of malicious code being introduced due to lack of established trust and project knowledge.
- Verify, as best as you can, that the new authors and reviewers are not malicious actors.
- If you are unsure, consider reverting the changes.
For commits approved by new reviewers:
- Why? New reviewers may not be familiar with the project's security requirements or may not have the expertise to identify malicious code.
- Verify, as best as you can, that the new reviewers are not malicious actors.
For commits made by new authors:
- Why? New contributors could potentially introduce security vulnerabilities, either accidentally or intentionally.
- Verify, as best as you can, that the new authors are not malicious actors.
- The fact that the reviewers are not new to the repository is a good sign.
Report created by dirty-waters.
Report created on 2025-06-17 05:42:02
|
@dependabot ignore @typescript-eslint/eslint-plugin minor version @dependabot ignore @typescript-eslint/parser minor version |
|
OK, I won't notify you about version 8.34.x of @typescript-eslint/eslint-plugin again, unless you unignore it. |
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/typescript-eslint-2e365290c6
branch
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 the typescript-eslint group with 2 updates: @typescript-eslint/eslint-plugin and @typescript-eslint/parser.
Updates
@typescript-eslint/eslint-pluginfrom 8.34.0 to 8.34.1Release notes
Sourced from
@typescript-eslint/eslint-plugin's releases.Changelog
Sourced from
@typescript-eslint/eslint-plugin's changelog.Commits
ccd0791chore(release): publish 8.34.13a8369dchore(eslint-plugin): switch auto-generated test cases to hand-written in no-...2fbae48chore(eslint-plugin): switch auto-generated test cases to hand-written in str...8a69a33chore(eslint-plugin): switch auto-generated test cases to hand-written in pre...58ce73fchore(eslint-plugin): switch auto-generated test cases to hand-written in no-...f9d4d10chore(eslint-plugin): switch auto-generated test cases to hand-written in no-...Updates
@typescript-eslint/parserfrom 8.34.0 to 8.34.1Release notes
Sourced from
@typescript-eslint/parser's releases.Changelog
Sourced from
@typescript-eslint/parser's changelog.Commits
ccd0791chore(release): publish 8.34.1Most Recent Ignore Conditions Applied to This Pull Request
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions