Skip to content
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

[Snyk] Upgrade bancos-brasileiros from 6.1.6 to 6.1.10 #622

Merged
merged 2 commits into from
Jan 5, 2025

Conversation

guibranco
Copy link
Owner

@guibranco guibranco commented Jan 4, 2025

User description

snyk-top-banner

Snyk has created this PR to upgrade bancos-brasileiros from 6.1.6 to 6.1.10.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: bancos-brasileiros
  • 6.1.10 - 2024-12-12

    Release of Bancos Brasileiros - v6.1.10

    • Added 1 bank
      • 663 - ACTUAL DTVM S.A. - 44.782.130/0001-07
    • Updated 2 banks
      • 634 - BCO TRIANGULO S.A. - 17.351.180/0001-59
        • Products (CTC): Null -> Cheque Especial, Troca de Modalidade
      • 662 - WE PAY OUT IP LTDA. - 32.708.748/0001-30
        • PixType (SPI): IDRT -> DRCT
        • DatePixStarted (SPI): 2024-07-03 15:28:02 -> 2024-12-09 11:10:00
  • 6.1.8 - 2024-12-12

    Release of Bancos Brasileiros - v6.1.8

    • Added 1 bank
      • 663 - ACTUAL DTVM S.A. - 44.782.130/0001-07
    • Updated 2 banks
      • 634 - BCO TRIANGULO S.A. - 17.351.180/0001-59
        • Products (CTC): Null -> Cheque Especial, Troca de Modalidade
      • 662 - WE PAY OUT IP LTDA. - 32.708.748/0001-30
        • PixType (SPI): IDRT -> DRCT
        • DatePixStarted (SPI): 2024-07-03 15:28:02 -> 2024-12-09 11:10:00
  • 6.1.6 - 2024-12-06

    Release of Bancos Brasileiros - v6.1.6

    • Added 1 bank
      • 674 - HINOVA PAY IP S.A. - 27.970.567/0001-47
    • Updated 1 bank
      • 523 - HR DIGITAL SCD - 44.292.580/0001-03
        • PixType (SPI): IDRT -> DRCT
        • DatePixStarted (SPI): 2024-06-10 06:02:13 -> 2024-12-05 11:10:00
from bancos-brasileiros GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Note

I'm currently writing a description for your pull request. I should be done shortly (<1 minute). Please don't edit the description field until I'm finished, or we may overwrite each other. If I find nothing to write about, I'll delete this message.


Description

  • Upgraded bancos-brasileiros from version 6.1.6 to 6.1.10 in both package.json and package-lock.json.
  • This update includes new features and improvements as per the latest release notes.
  • Ensures the project is using the latest version for better security and functionality.

Changes walkthrough 📝

Relevant files
Dependencies
package-lock.json
Upgrade bancos-brasileiros in package-lock.json                   

examples/emberjs/package-lock.json

  • Updated bancos-brasileiros version from 6.1.6 to 6.1.10.
  • Adjusted integrity hash for the new version.
  • +7/-7     
    package.json
    Upgrade bancos-brasileiros in package.json                             

    examples/emberjs/package.json

    • Updated bancos-brasileiros version from 6.1.6 to 6.1.10.
    +1/-1     

    💡 Penify usage:
    Comment /help on the PR to get a list of all available Penify tools and their descriptions

    Snyk has created this PR to upgrade bancos-brasileiros from 6.1.6 to 6.1.10.
    
    See this package in npm:
    bancos-brasileiros
    
    See this project in Snyk:
    https://app.snyk.io/org/guibranco/project/337dc2ee-ac4c-4ec7-8f33-7fddb26040de?utm_source=github&utm_medium=referral&page=upgrade-pr
    Copy link

    sourcery-ai bot commented Jan 4, 2025

    Reviewer's Guide by Sourcery

    This pull request upgrades the bancos-brasileiros npm package from version 6.1.6 to 6.1.10. This addresses updates to three banks, including the addition of one new bank and modifications to two existing banks.

    ER diagram showing bank data structure changes

    erDiagram
        BANK {
            string code
            string name
            string cnpj
            string products
            string pixType
            datetime datePixStarted
        }
    
        %% New bank added
        ACTUAL_DTVM {
            string code "663"
            string name "ACTUAL DTVM S.A."
            string cnpj "44.782.130/0001-07"
        }
    
        %% Updated banks
        BCO_TRIANGULO {
            string code "634"
            string products "Cheque Especial, Troca de Modalidade"
        }
    
        WE_PAY_OUT {
            string code "662"
            string pixType "DRCT"
            datetime datePixStarted "2024-12-09 11:10:00"
        }
    
        BANK ||--o| ACTUAL_DTVM : "new"
        BANK ||--o| BCO_TRIANGULO : "updated"
        BANK ||--o| WE_PAY_OUT : "updated"
    
    Loading

    File-Level Changes

    Change Details Files
    Upgrade dependency bancos-brasileiros
    • Updated the version of bancos-brasileiros from 6.1.6 to 6.1.10 in package.json
    • Regenerated the package-lock.json file to reflect the updated dependency
    examples/emberjs/package.json
    examples/emberjs/package-lock.json

    Tips and commands

    Interacting with Sourcery

    • Trigger a new review: Comment @sourcery-ai review on the pull request.
    • Continue discussions: Reply directly to Sourcery's review comments.
    • Generate a GitHub issue from a review comment: Ask Sourcery to create an
      issue from a review comment by replying to it.
    • Generate a pull request title: Write @sourcery-ai anywhere in the pull
      request title to generate a title at any time.
    • Generate a pull request summary: Write @sourcery-ai summary anywhere in
      the pull request body to generate a PR summary at any time. You can also use
      this command to specify where the summary should be inserted.

    Customizing Your Experience

    Access your dashboard to:

    • Enable or disable review features such as the Sourcery-generated pull request
      summary, the reviewer's guide, and others.
    • Change the review language.
    • Add, remove or edit custom review instructions.
    • Adjust other review settings.

    Getting Help

    @gstraccini gstraccini bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Jan 4, 2025
    Copy link

    coderabbitai bot commented Jan 4, 2025

    Important

    Review skipped

    Ignore keyword(s) in the title.

    Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

    You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


    🪧 Tips

    Chat

    There are 3 ways to chat with CodeRabbit:

    • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
      • I pushed a fix in commit <commit_id>, please review it.
      • Generate unit testing code for this file.
      • Open a follow-up GitHub issue for this discussion.
    • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
      • @coderabbitai generate unit testing code for this file.
      • @coderabbitai modularize this function.
    • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
      • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
      • @coderabbitai read src/utils.ts and generate unit testing code.
      • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
      • @coderabbitai help me debug CodeRabbit configuration file.

    Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

    CodeRabbit Commands (Invoked using PR comments)

    • @coderabbitai pause to pause the reviews on a PR.
    • @coderabbitai resume to resume the paused reviews.
    • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
    • @coderabbitai full review to do a full review from scratch and review all the files again.
    • @coderabbitai summary to regenerate the summary of the PR.
    • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
    • @coderabbitai resolve resolve all the CodeRabbit review comments.
    • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
    • @coderabbitai help to get help.

    Other keywords and placeholders

    • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
    • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
    • Add @coderabbitai anywhere in the PR title to generate the title automatically.

    CodeRabbit Configuration File (.coderabbit.yaml)

    • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
    • Please see the configuration documentation for more information.
    • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

    Documentation and Community

    • Visit our Documentation for detailed information on how to use CodeRabbit.
    • Join our Discord Community to get help, request features, and share feedback.
    • Follow us on X/Twitter for updates and announcements.

    Copy link

    @sourcery-ai sourcery-ai bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

    @github-actions github-actions bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 4, 2025
    @penify-dev penify-dev bot added the enhancement A enhancement to the project label Jan 4, 2025
    Copy link

    @korbit-ai korbit-ai bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    I've completed my review and didn't find any issues.

    Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

    Korbit Guide: Usage and Customization

    Interacting with Korbit

    • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
    • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
    • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
    • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
    • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

    Customizing Korbit

    • Check out our docs on how you can make Korbit work best for you and your team.
    • Customize Korbit for your organization through the Korbit Console.

    Current Korbit Configuration

    General Settings
    Setting Value
    Review Schedule Automatic excluding drafts
    Max Issue Count 10
    Automatic PR Descriptions
    Issue Categories
    Category Enabled
    Naming
    Database Operations
    Documentation
    Logging
    Error Handling
    Systems and Environment
    Objects and Data Structures
    Readability and Maintainability
    Asynchronous Processing
    Design Patterns
    Third-Party Libraries
    Performance
    Security
    Functionality

    Feedback and Support

    Note

    Korbit Pro is free for open source projects 🎉

    Looking to add Korbit to your team? Get started with a free 2 week trial here

    Copy link
    Contributor

    penify-dev bot commented Jan 4, 2025

    PR Review 🔍

    ⏱️ Estimated effort to review [1-5]

    1, because this PR only involves updating a dependency version with no complex changes.

    🧪 Relevant tests

    No

    ⚡ Possible issues

    No

    🔒 Security concerns

    No

    Copy link

    socket-security bot commented Jan 4, 2025

    New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

    Package New capabilities Transitives Size Publisher
    npm/[email protected] None 0 323 kB guibranco

    🚮 Removed packages: npm/[email protected]

    View full report↗︎

    Copy link

    socket-security bot commented Jan 4, 2025

    🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

    To accept the risk, merge this PR and you will not be notified again.

    Alert Package NoteSourceCI
    Unpopular package npm/[email protected] 🚫

    View full report↗︎

    Next steps

    What are unpopular packages?

    This package is not very popular.

    Unpopular packages may have less maintenance and contain other problems.

    Take a deeper look at the dependency

    Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

    Remove the package

    If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

    Mark a package as acceptable risk

    To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

    Copy link
    Contributor

    penify-dev bot commented Jan 4, 2025

    PR Code Suggestions ✨

    CategorySuggestion                                                                                                                                    Score
    Testing
    Execute tests to confirm no breaking changes occur after the upgrade

    Consider running tests after the upgrade to ensure that the new version does not introduce
    any breaking changes.

    examples/emberjs/package-lock.json [12]

    -"bancos-brasileiros": "^6.1.10"
    +"bancos-brasileiros": "^6.1.10" // Run tests post-upgrade
     
    Suggestion importance[1-10]: 9

    Why: Running tests post-upgrade is a critical step to ensure stability and functionality, making this suggestion highly relevant and actionable.

    9
    Security
    Ensure the integrity hash is verified for security

    Validate the integrity hash for bancos-brasileiros to ensure the package has not been
    tampered with.

    examples/emberjs/package-lock.json [4885]

    -"integrity": "sha512-Symo1Q8zxbJVzClH+b73cddrS7xh4PzIITbM+RpsoNd3JgYu7BWkbdO2+Zr4TuSW17mtaLg9EK2LpYHdoR9R8A=="
    +"integrity": "sha512-Symo1Q8zxbJVzClH+b73cddrS7xh4PzIITbM+RpsoNd3JgYu7BWkbdO2+Zr4TuSW17mtaLg9EK2LpYHdoR9R8A==" // Validate integrity
     
    Suggestion importance[1-10]: 8

    Why: Validating the integrity hash is crucial for security, and the suggestion correctly highlights the need for this verification.

    8
    Performance
    Assess the impact of the version upgrade on application performance

    Review the impact of upgrading bancos-brasileiros on the overall application functionality
    and performance.

    examples/emberjs/package.json [70]

    -"bancos-brasileiros": "^6.1.10"
    +"bancos-brasileiros": "^6.1.10" // Review impact on functionality and performance
     
    Suggestion importance[1-10]: 7

    Why: Assessing the impact of a version upgrade is important for maintaining application performance, though the suggestion lacks specific metrics or criteria for review.

    7
    Compatibility
    Check for compatibility of the new version with existing dependencies

    Ensure that the versioning of bancos-brasileiros is compatible with other dependencies in
    the project to avoid potential conflicts.

    examples/emberjs/package-lock.json [12]

    -"bancos-brasileiros": "^6.1.10"
    +"bancos-brasileiros": "^6.1.10" // Ensure compatibility with other dependencies
     
    Suggestion importance[1-10]: 6

    Why: While ensuring compatibility is important, the suggestion does not provide actionable steps or checks to perform, making it less impactful.

    6

    Copy link
    Contributor

    github-actions bot commented Jan 4, 2025

    Summary

    Status Count
    🔍 Total 455
    ✅ Successful 233
    ⏳ Timeouts 2
    🔀 Redirected 0
    👻 Excluded 220
    ❓ Unknown 0
    🚫 Errors 0

    Errors per input

    Errors in ./README.md

    Errors in ./README.pt-br.md

    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun failed workflows

    Copy link
    Contributor

    gstraccini bot commented Jan 4, 2025

    Rerunning 0 failed workflows on the commit 0dda36827a2d6e35080dc6e15faba84745b90f59! 🔁

    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun workflows failure

    Copy link
    Contributor

    gstraccini bot commented Jan 5, 2025

    I'm sorry @guibranco, I can't do that. Command not found. 🥺

    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun workflows failure

    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun workflows cancelled

    1 similar comment
    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun workflows cancelled

    Copy link
    Contributor

    gstraccini bot commented Jan 5, 2025

    Rerunning 5 cancelled workflows on the commit 0dda36827a2d6e35080dc6e15faba84745b90f59! 🔁

    Copy link
    Contributor

    github-actions bot commented Jan 5, 2025

    Infisical secrets check: ✅ No secrets leaked!

    💻 Scan logs
    10:25PM INF scanning for exposed secrets...
    10:25PM INF 1079 commits scanned.
    10:25PM INF scan completed in 2.66s
    10:25PM INF no leaks found
    

    @guibranco
    Copy link
    Owner Author

    @gstraccini rerun workflows cancelled

    Copy link
    Contributor

    gstraccini bot commented Jan 5, 2025

    Rerunning 4 cancelled workflows on the commit 0dda36827a2d6e35080dc6e15faba84745b90f59! 🔁

    Copy link
    Contributor

    gstraccini bot commented Jan 5, 2025

    Rerunning the following workflows:

    Copy link

    sonarqubecloud bot commented Jan 5, 2025

    @guibranco guibranco merged commit 5db0927 into main Jan 5, 2025
    45 of 46 checks passed
    @guibranco guibranco deleted the snyk-upgrade-fabe56970cca5444d52175cf96f8df4c branch January 5, 2025 23:50
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) enhancement A enhancement to the project Review effort [1-5]: 1 size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants