Upgrade bancos-brasileiros from 6.0.69 to 6.0.77

[guibranco]

User description

Snyk has created this PR to upgrade bancos-brasileiros from 6.0.69 to 6.0.77.

ℹ️ 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 on 22 days ago.

Release notes

Package name: bancos-brasileiros

• 6.0.77 - 2024-09-15
  

  Release of Bancos Brasileiros - v6.0.77

  • Updated 1 bank
    • 597 - ISSUER IP LTDA. - 34.747.388/0001-00
      • PixType (SPI): IDRT -> DRCT
      • DatePixStarted (SPI): 2024-05-17 09:47:12 -> 2024-09-05 10:10:00
• 6.0.76 - 2024-09-14
  

  Release of Bancos Brasileiros - v6.0.76

  • Updated 1 bank
    • 597 - ISSUER IP LTDA. - 34.747.388/0001-00
      • PixType (SPI): IDRT -> DRCT
      • DatePixStarted (SPI): 2024-05-17 09:47:12 -> 2024-09-05 10:10:00
• 6.0.75 - 2024-09-13
  

  Release of Bancos Brasileiros - v6.0.75

  • Updated 1 bank
    • 597 - ISSUER IP LTDA. - 34.747.388/0001-00
      • PixType (SPI): IDRT -> DRCT
      • DatePixStarted (SPI): 2024-05-17 09:47:12 -> 2024-09-05 10:10:00
• 6.0.72 - 2024-09-13
  

  Release of Bancos Brasileiros - v6.0.72

  • Updated 1 bank
    • 597 - ISSUER IP LTDA. - 34.747.388/0001-00
      • PixType (SPI): IDRT -> DRCT
      • DatePixStarted (SPI): 2024-05-17 09:47:12 -> 2024-09-05 10:10:00
• 6.0.71 - 2024-09-13
• 6.0.69 - 2024-09-06
  

  Release of Bancos Brasileiros - v6.0.69

  • Updated 1 bank
    • 597 - ISSUER IP LTDA. - 34.747.388/0001-00
      • PixType (SPI): IDRT -> DRCT
      • DatePixStarted (SPI): 2024-05-17 09:47:12 -> 2024-09-05 10: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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Description

• Upgraded bancos-brasileiros from version 6.0.69 to 6.0.77 in both package-lock.json and package.json.
• This update includes security improvements and new features as per the release notes.
• The new version was released 22 days ago and is 5 versions ahead of the current version.

---

Changes walkthrough 📝

Relevant files

Dependencies

package-lock.json Upgrade bancos-brasileiros dependency in package-lock.json examples/emberjs/package-lock.json Updated bancos-brasileiros dependency from version 6.0.69 to 6.0.77. Updated integrity hash for the new version. +7/-7      package.json Upgrade bancos-brasileiros dependency in package.json        examples/emberjs/package.json Updated bancos-brasileiros dependency from version 6.0.69 to 6.0.77. +1/-1

---

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

Summary by CodeRabbit

• Chores
  • Updated the bancos-brasileiros package dependency to the latest version for improved performance and security.

[coderabbitai]

Walkthrough

The package.json file for the emberjs project has been updated to change the version of the bancos-brasileiros package from ^6.0.69 to ^6.0.77. This change is limited to the dependencies section, with no other modifications to the structure or scripts within the file.

Changes

File	Change Summary
examples/emberjs/package.json	Updated bancos-brasileiros version from ^6.0.69 to ^6.0.77

Possibly related PRs

• Upgrade bancos-brasileiros from 6.0.51 to 6.0.62 #537: This PR updates the bancos-brasileiros package from ^6.0.51 to ^6.0.62, which is a direct predecessor to the version updated in the main PR.
• Upgrade bancos-brasileiros from 6.0.62 to 6.0.67 #548: This PR updates the bancos-brasileiros package from ^6.0.62 to ^6.0.67, continuing the version progression leading up to the main PR.
• Upgrade bancos-brasileiros from 6.0.67 to 6.0.69 #554: This PR updates the bancos-brasileiros package from ^6.0.67 to ^6.0.69, which is also a direct predecessor to the version updated in the main PR.

Suggested labels

size/S, Review effort [1-5]: 1

Suggested reviewers

• gstraccini

🐇 In the meadow, I hop with glee,
A version change, oh joy for me!
From 69 to 77, we leap,
In the world of code, our secrets keep.
With each update, we grow so bright,
Hopping along, everything feels right! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ee08a2a and 60ea4cc.

⛔ Files ignored due to path filters (1)

• examples/emberjs/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• examples/emberjs/package.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

examples/emberjs/package.json (1)

70-70: LGTM! Verify impact on project functionality.

The update of bancos-brasileiros from ^6.0.69 to ^6.0.77 looks good. This minor version update should be backward-compatible.

However, given the changes mentioned in the release notes (updates to ISSUER IP LTDA., including modifications to PixType and DatePixStarted fields), it's important to:

1. Review the full changelog to understand all changes between versions 6.0.69 and 6.0.77.
2. Verify that this update doesn't negatively impact your project's functionality, especially if you're using features related to ISSUER IP LTDA. or the modified fields.
3. Run your test suite to ensure no regressions.

To help verify the impact, you can run the following script to check for usage of the affected fields:

If these searches return results, pay extra attention to those areas of your code during testing.

✅ Verification successful

Verify schema compatibility with updated bancos-brasileiros package.

The bancos-brasileiros package has been updated, and PixType and DatePixStarted are utilized in schemas/typescript.ts and schemas/javascript.js. Please ensure that the changes in these schemas are compatible with the updated package version.

• Files to review:
  • schemas/typescript.ts
  • schemas/javascript.js

Ensure that any modifications to PixType and DatePixStarted in these schemas align with the changes introduced in version ^6.0.77 of bancos-brasileiros.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for usage of PixType and DatePixStarted in the project

echo "Searching for PixType usage:"
rg --type js --type ts 'PixType'

echo "Searching for DatePixStarted usage:"
rg --type js --type ts 'DatePixStarted'

Length of output: 704

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because this PR only involves updating a dependency version with no changes to the code logic.
🧪 Relevant tests	Yes
⚡ Possible issues	No
🔒 Security concerns	No

[socket-security]

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

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

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 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	Note	Source	CI
Unpopular package	npm/[email protected]	Location: Package overview	examples/emberjs/package-lock.json examples/emberjs/package.json	🚫

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

• @SocketSecurity ignore npm/[email protected]

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

12:21AM INF scanning for exposed secrets...
12:21AM INF 988 commits scanned.
12:21AM INF scan completed in 2.56s
12:21AM INF no leaks found

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Testing	Run tests to verify application behavior after the upgrade Consider running tests after upgrading to ensure that the application behaves as expected with the new version. examples/emberjs/package-lock.json [12] -"bancos-brasileiros": "^6.0.77" +"bancos-brasileiros": "^6.0.77" // Run tests post-upgrade Suggestion importance[1-10]: 8 Why: Running tests post-upgrade is a strong recommendation to ensure application stability, and it is a practical step that can help catch issues early.	8
Security	Verify the integrity hash for the new version Consider verifying the integrity hash for the new version to ensure the package has not been tampered with. examples/emberjs/package-lock.json [4885] -"integrity": "sha512-8AHFtcE7haY1PXceAsDX4yVOIpmPNDVqwngcim0lo1mRNyYiirBR19xRwbofeUBjQxjvxj4THS7rb2+3SX7J7Q==" +"integrity": "sha512-8AHFtcE7haY1PXceAsDX4yVOIpmPNDVqwngcim0lo1mRNyYiirBR19xRwbofeUBjQxjvxj4THS7rb2+3SX7J7Q==" // Verify integrity Suggestion importance[1-10]: 7 Why: Verifying the integrity hash is a good security practice, but the suggestion does not specify how to perform this verification, which limits its usefulness.	7
Compatibility	Check for breaking changes in the new version Ensure that the new version of bancos-brasileiros does not introduce breaking changes that could affect the application. examples/emberjs/package.json [70] -"bancos-brasileiros": "^6.0.77" +"bancos-brasileiros": "^6.0.77" // Check for breaking changes Suggestion importance[1-10]: 6 Why: Checking for breaking changes is crucial, but the suggestion lacks specific guidance on how to check for these changes, making it less actionable.	6
	Check compatibility of the new version with existing dependencies Ensure that the version of bancos-brasileiros is compatible with other dependencies in the project to avoid potential conflicts. examples/emberjs/package-lock.json [12] -"bancos-brasileiros": "^6.0.77" +"bancos-brasileiros": "^6.0.77" // Ensure compatibility Suggestion importance[1-10]: 5 Why: While ensuring compatibility is important, the suggestion does not provide actionable steps or checks to perform, making it more of a general reminder than a specific improvement.	5

[github-actions]

Summary

Status	Count
🔍 Total	462
✅ Successful	359
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	102
❓ Unknown	0
🚫 Errors	1

Errors per input

Errors in ./CHANGELOG.md

• [429] https://github.com/silverio27 | Failed: Network error: Too Many Requests
  Full Github Actions output

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud