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.10 to 6.1.22 #624

Merged
merged 3 commits into from
Jan 11, 2025

Conversation

guibranco
Copy link
Owner

@guibranco guibranco commented Jan 11, 2025

User description

snyk-top-banner

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

ℹ️ 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 5 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: bancos-brasileiros
  • 6.1.22 - 2024-12-20

    Release of Bancos Brasileiros - v6.1.22

    • Updated 1 bank
      • 95 - BANCO TRAVELEX S.A. - 11.703.662/0001-44
        • LongName (STR): Travelex Banco de CYmbio S.A. -> BANCO TRAVELEX S.A.
        • ShortName (STR): TRAVELEX BANCO DE CAMBIO S.A. -> BANCO TRAVELEX S.A.
  • 6.1.21 - 2024-12-19

    Release of Bancos Brasileiros - v6.1.21

    • Updated 2 banks
      • 450 - FITBANK IP - 13.203.354/0001-85
        • LongName (STR): FITBANK INSTITUI?AO DE PAGAMENTOS ELETRONICOS S.A. -> FITBANK INSTITUI?AO DE PAGAMENTO S.A.
      • 559 - KANASTRA CFI - 49.288.113/0001-23
        • LongName (STR): KANASTRA SOCIEDADE DE CR?DITO DIRETO S.A. -> KANASTRA FINANCEIRA S.A, CREDITO, FINANCIAMENTO E INVESTIMENTO
        • ShortName (STR): KANASTRA SCD -> KANASTRA CFI
  • 6.1.18 - 2024-12-19

    Release of Bancos Brasileiros - v6.1.18

    • Updated 2 banks
      • 450 - FITBANK IP - 13.203.354/0001-85
        • LongName (STR): FITBANK INSTITUI?AO DE PAGAMENTOS ELETRONICOS S.A. -> FITBANK INSTITUI?AO DE PAGAMENTO S.A.
      • 559 - KANASTRA CFI - 49.288.113/0001-23
        • LongName (STR): KANASTRA SOCIEDADE DE CR?DITO DIRETO S.A. -> KANASTRA FINANCEIRA S.A, CREDITO, FINANCIAMENTO E INVESTIMENTO
        • ShortName (STR): KANASTRA SCD -> KANASTRA CFI
  • 6.1.12 - 2024-12-19

    Release of Bancos Brasileiros - v6.1.12

    • Updated 2 banks
      • 450 - FITBANK IP - 13.203.354/0001-85
        • LongName (STR): FITBANK INSTITUI?AO DE PAGAMENTOS ELETRONICOS S.A. -> FITBANK INSTITUI?AO DE PAGAMENTO S.A.
      • 559 - KANASTRA CFI - 49.288.113/0001-23
        • LongName (STR): KANASTRA SOCIEDADE DE CR?DITO DIRETO S.A. -> KANASTRA FINANCEIRA S.A, CREDITO, FINANCIAMENTO E INVESTIMENTO
        • ShortName (STR): KANASTRA SCD -> KANASTRA CFI
  • 6.1.11 - 2024-12-17

    Release of Bancos Brasileiros - v6.1.11

    • Added 1 bank
      • 666 - URBANO S.A. SCFI - 53.842.122/0001-91
  • 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
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:


Description

  • Upgraded bancos-brasileiros dependency from version 6.1.10 to 6.1.22 to keep the project up-to-date.
  • This upgrade includes important updates and fixes from the latest version.

Changes walkthrough 📝

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

examples/emberjs/package-lock.json

  • Upgraded bancos-brasileiros from version 6.1.10 to 6.1.22.
  • Updated integrity hashes for the new version.
  • +7/-7     
    package.json
    Update bancos-brasileiros version in package.json               

    examples/emberjs/package.json

  • Changed bancos-brasileiros dependency version from ^6.1.10 to ^6.1.22.

  • +1/-1     

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

    Description by Korbit AI

    What change is being made?

    Upgrade bancos-brasileiros dependency from version 6.1.10 to 6.1.22 in the Ember.js example project, and add .config/dotnet-tools.json to include the C# formatter tool, CSharpier.

    Why are these changes being made?

    The bancos-brasileiros library is being upgraded to ensure compatibility with newer updates that may include bug fixes, performance improvements, or new features. Adding CSharpier as a development tool standardizes code formatting, improving code consistency and readability in projects using C#.

    Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

    Snyk has created this PR to upgrade bancos-brasileiros from 6.1.10 to 6.1.22.
    
    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 11, 2025

    Reviewer's Guide by Sourcery

    This pull request upgrades the bancos-brasileiros npm package from version 6.1.10 to 6.1.22. Several updates to bank information are included in this version bump, impacting names, products, and Pix information.

    Class diagram showing bank information updates

    classDiagram
        class Bank {
            +String code
            +String longName
            +String shortName
            +String cnpj
            +String[] products
            +String pixType
            +DateTime datePixStarted
        }
    
        note for Bank "Changes in bank names, products, and Pix info across versions 6.1.10 to 6.1.22"
    
        class TravelexBank {
            +String longName
            +String shortName
        }
        class FitBank {
            +String longName
        }
        class KanastraBank {
            +String longName
            +String shortName
        }
        class TrianguloBank {
            +String[] products
        }
        class WePayOut {
            +String pixType
            +DateTime datePixStarted
        }
    
        Bank <|-- TravelexBank
        Bank <|-- FitBank
        Bank <|-- KanastraBank
        Bank <|-- TrianguloBank
        Bank <|-- WePayOut
    
    Loading

    File-Level Changes

    Change Details Files
    Upgraded bancos-brasileiros from 6.1.10 to 6.1.22.
    • Updated the dependency version in package.json
    examples/emberjs/package.json
    Updated package lock file.
    • Regenerated the lockfile to reflect updated dependency
    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

    Copy link

    coderabbitai bot commented Jan 11, 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 11, 2025
    @penify-dev penify-dev bot added enhancement A enhancement to the project Review effort [1-5]: 1 labels Jan 11, 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 11, 2025

    PR Review 🔍

    ⏱️ Estimated effort to review [1-5]

    1, because this PR only updates the version of a dependency and does not introduce any new logic or complexity.

    🧪 Relevant tests

    No

    ⚡ Possible issues

    No

    🔒 Security concerns

    No

    Copy link

    socket-security bot commented Jan 11, 2025

    Updated dependencies detected. Learn more about Socket for GitHub ↗︎

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

    View full report↗︎

    Copy link
    Contributor

    penify-dev bot commented Jan 11, 2025

    PR Code Suggestions ✨

    CategorySuggestion                                                                                                                                    Score
    Security
    Verify the integrity hash for the updated package version

    Ensure that the integrity hash for the new version of bancos-brasileiros is correct and
    matches the published package to avoid potential security issues.

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

    -"integrity": "sha512-nw2hJMGjztKKOYzT8CncfVmWAKCOjDV1uJ2i9RpEmEdP/x+BFzFTkRRHZwL9QYHf1Laz2h3GKEU8bYVLISeW2w=="
    +"integrity": "<correct-integrity-hash>"
     
    Suggestion importance[1-10]: 8

    Why: Verifying the integrity hash is crucial for security, as it ensures that the package has not been tampered with. However, the suggestion does not provide the correct hash, which is necessary for full implementation.

    8
    Ensure the new package version is free of known vulnerabilities

    Validate that the new version of bancos-brasileiros does not introduce any vulnerabilities
    by checking against a security database.

    examples/emberjs/package.json [70]

    -"bancos-brasileiros": "^6.1.22"
    +"bancos-brasileiros": "^6.1.22" // Check for vulnerabilities
     
    Suggestion importance[1-10]: 8

    Why: Ensuring that the new package version is free of known vulnerabilities is a significant security measure. The suggestion is relevant and important, but it could be more actionable.

    8
    Possible issue
    Review breaking changes for compatibility with the new package version

    Check if there are any breaking changes in the bancos-brasileiros package between versions
    6.1.10 and 6.1.22 to ensure compatibility.

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

    -"bancos-brasileiros": "^6.1.22"
    +"bancos-brasileiros": "^6.1.22" // Ensure compatibility
     
    Suggestion importance[1-10]: 7

    Why: This suggestion addresses potential compatibility issues, which is important when updating dependencies. However, it lacks specific guidance on how to check for breaking changes.

    7
    Check the accessibility of the resolved URL for the updated package version

    Confirm that the resolved URL for the new version of bancos-brasileiros is correct and
    accessible to avoid issues during installation.

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

    -"resolved": "https://registry.npmjs.org/bancos-brasileiros/-/bancos-brasileiros-6.1.22.tgz"
    +"resolved": "https://registry.npmjs.org/bancos-brasileiros/-/bancos-brasileiros-6.1.22.tgz" // Verify URL
     
    Suggestion importance[1-10]: 6

    Why: While checking the URL's accessibility is a good practice, it is less critical than the other suggestions. The suggestion is valid but does not address a major security or compatibility concern.

    6

    @guibranco
    Copy link
    Owner Author

    @gstraccini csharpier

    Copy link
    Contributor

    gstraccini bot commented Jan 11, 2025

    Running CSharpier on this branch! 🔧

    Copy link
    Contributor

    gstraccini bot commented Jan 11, 2025

    CSharpier result:

    Formatted 2 files in 352ms.
    
    

    Copy link
    Contributor

    Infisical secrets check: ✅ No secrets leaked!

    💻 Scan logs
    1:51PM INF scanning for exposed secrets...
    1:51PM INF 1088 commits scanned.
    1:51PM INF scan completed in 2.67s
    1:51PM INF no leaks found
    

    @guibranco guibranco merged commit c3e0a57 into main Jan 11, 2025
    43 checks passed
    @guibranco guibranco deleted the snyk-upgrade-5c500ef8c5c1b433a193164792c1363d branch January 11, 2025 14:11
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    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