-
Notifications
You must be signed in to change notification settings - Fork 6
Downgrade jackson to 2.21.* #100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: cryptomator/integrations-api
Length of output: 1830
🌐 Web query:
GitHub Dependabot ignore versions security updates update-types ignore rules official documentation💡 Result:
You can configure Dependabot ignore rules in your.github/dependabot.yml file using the ignore option. These rules allow you to exclude specific dependencies, versions, or types of updates from Dependabot pull requests [1][2]. Configuration Structure The ignore option is defined under each package-ecosystem entry within the updates section of your dependabot.yml file [2][3]. Supported ignore parameters include: dependency-name: Specifies the dependency to ignore. You can use a wildcard (*) to match multiple dependencies [2][3]. versions: Allows you to specify particular versions or ranges of versions to ignore [2][3]. update-types: Used to ignore specific semantic versioning (SemVer) levels [2]. Supported values are version-update:semver-patch, version-update:semver-minor, and version-update:semver-major [2]. Important Limitations It is critical to note that the update-types setting only applies to version updates; it does not affect security updates [1][2]. Security updates are intended to be processed regardless of your update-types configuration [1][2]. Alternative Methods In addition to the dependabot.yml file, you can also manage ignores directly via pull requests using comment commands [1][4]. By commenting
@dependabotignore on a Dependabot pull request, you can instruct Dependabot to ignore updates for specific dependencies or versions [1][4]. You can later use@dependabotunignore to remove these constraints [4]. For further granular control, the ignore option can be used in conjunction with the allow option to define exactly which dependencies to maintain [2]. If a dependency is matched by both an allow and an ignore rule, it will be ignored [2].Citations:
🌐 Web query:
site:docs.github.com Dependabot ignore versions security updates "ignore" "security updates"💡 Result:
You can manage Dependabot's behavior regarding security updates and version updates by using the
ignoreoption in yourdependabot.ymlconfiguration file or by using@dependabotcomment commands on pull requests [1][2]. Both methods allow you to ignore specific dependencies, specific versions, or specific update types (like major, minor, or patch) [3][1][2]. Configuration in dependabot.yml You can define anignoreblock within theupdatessection for a package ecosystem in yourdependabot.ymlfile [4][1]. This configuration applies to both version updates and security updates [1][2]. Example syntax: updates: - package-ecosystem: "npm" directory: "/" ignore: - dependency-name: "lodash" versions: ["< 4.17.0"] - dependency-name: "express" update-types: ["version-update:semver-major"] When using theignoreoption, Dependabot first checks for all explicitly allowed dependencies and then filters out any that are ignored [3][5]. If a dependency is matched by both anallowand anignorestatement, it will be ignored [3][5]. Using Comment Commands Alternatively, you can manage ignore conditions directly on an open Dependabot pull request using@dependabotcommands [1][2]. These commands are effective for quickly ignoring updates without modifying your configuration file [6]. Common commands include: -@dependabotignore DEPENDENCY_NAME: Prevents future updates for the specified dependency [6]. -@dependabotignore DEPENDENCY_NAME major version: Prevents updates to the major version [6]. -@dependabotunignore...: Clears existing ignore conditions [1][6]. Note on Security Updates: Whileignoreconfigurations apply to both version and security updates, Dependabot generally prioritizes security [2]. If you are specifically looking to disable all "version updates" while keeping "security updates," you can setopen-pull-requests-limit: 0for a specificpackage-ecosystemin yourdependabot.ymlfile [4]. This ensures that Dependabot does not open pull requests for non-security version updates, effectively limiting activity to security-related patches [4].Citations:
🏁 Script executed:
Repository: cryptomator/integrations-api
Length of output: 383
Preserve Jackson security updates.
The
ignore.versionsrule excludes Jackson2.22and newer from both version and security updates. If routine minor and major upgrades must remain blocked, replace it withupdate-types; security updates will remain eligible.🤖 Prompt for AI Agents