chore: update dependencies #1431
Open
+142
−82
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
b2363df to
c7f5caf
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
c8d91f2 to
e7035d7
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
e7035d7 to
8fc6a5f
Compare
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.
Update Request | Renovate Bot
This PR contains the following updates:
^22.17.1->^24.0.0^0.7.0->^0.8.0v2.8.3->v3.3.0v1.36.3->v1.38.0v1.29.14->v1.31.0v1.17.67->v1.18.4v1.17.49->v1.18.4v1.22.3->v1.22.5v5.0.2->v5.0.3v5.35.0->v5.36.1v1.8.0->v1.9.0v4.1.0->v4.1.2v1.4.2->v1.4.3v10.26.0->v10.27.0v4.5.2->v5.3.0v0.20.3->v0.20.6v1.4.0->v2.3.2v2.26.3->v2.27.1v1.16.0->v1.20.0v0.9.0->v0.10.05c39aec->ed9094b79df5c4->ba97887v0.5001.0->v0.5200.0v1.22.0->v1.23.0v0.63.0->v0.65.0v6.0.1->v6.0.2v1.3.1->v1.4.0v0.1.11->v0.1.13v1.0.10->v1.0.11v0.3.6->v0.3.7v0.2.23->v0.2.25v0.7.0->v0.8.1v0.49.0->v1.0.166b1371->34930b2v0.0.0-20220527175918-f17b0f05cf2c->v2.4.0v0.6.1->v0.7.0v3.38.1->v3.44.0v1.4.0->v1.4.2v3.5.21->v3.6.4v3.5.21->v3.6.4v3.5.21->v3.6.4v0.5.0->v0.5.2v0.39.0->v0.41.0v0.41.0->v0.43.0v0.10.0->v0.16.0v0.15.0->v0.16.0v0.32.0->v0.34.0v0.26.0->v0.28.0v0.11.0->v0.12.0v0.33.0->v0.36.0436f7fd->f333402v1.73.0->v1.74.2v1.36.6->v1.36.7v2.4.0->v3.0.11.18->1.20v0.34.0-alpha.0->v0.34.0-rc.1v0.34.0-alpha.0->v0.34.0-rc.1v0.34.0-alpha.0->v11.0.0+incompatible22-alpine->24-alpinev0.20.4->v0.21.0Release Notes
vuejs/tsconfig (@vue/tsconfig)
v0.8.0Compare Source
Breaking Changes
libReplacementfor better performance by @ntnyq in https://github.com/vuejs/tsconfig/pull/35noUncheckedIndexedAccessandexactOptionalPropertyTypesby @haoqunjiang in https://github.com/vuejs/tsconfig/pull/36If you experience a significant number of type errors in your projects after upgrading to this version, you might want to consider a gradual approach to adopting the new options:
@vue/tsconfig, usesupress-ts-errors(npx suppress-ts-errors && npx suppress-ts-errors vue src/**/*.vue) to insert@ts-expect-errorcomments in your current codebase.Full Changelog: vuejs/tsconfig@v0.7.0...v0.8.0
ProtonMail/gopenpgp (github.com/ProtonMail/gopenpgp/v2)
v3.3.0Compare Source
What's Changed
Added
Changed
Full Changelog: ProtonMail/gopenpgp@v3.2.1...v3.3.0
v3.2.1Compare Source
What's Changed
Fixed
Full Changelog: ProtonMail/gopenpgp@v3.2.0...v3.2.1
v3.2.0Compare Source
What's Changed
Added
Changed
1.22.0.v1.2.0.pkgs/errorsdependency.Full Changelog: ProtonMail/gopenpgp@v3.1.3...v3.2.0
v3.1.3Compare Source
What's Changed
Changed
v1.1.6Full Changelog: ProtonMail/gopenpgp@v3.1.2...v3.1.3
v3.1.2Compare Source
What's Changed
Changed
v1.1.5Full Changelog: ProtonMail/gopenpgp@v3.1.1...v3.1.2
v3.1.1Compare Source
What's Changed
Changed
v1.1.4Full Changelog: ProtonMail/gopenpgp@v3.1.0...v3.1.1
v3.1.0Compare Source
What's Changed
Added
Changed
profile.Custom.AllowWeakRSAtoprofile.Custom.InsecureAllowWeakRSAv1.1.3Full Changelog: ProtonMail/gopenpgp@v3.0.0...v3.1.0
v3.0.0Compare Source
What's Changed
New simplified and unified API
GopenPGP v3 introduces a new unified API for high level OpenPGP operations. In comparison to GopenPGP v2, where similar functions were dispersed across different types and required varying implementations for the same operations, GopenPGP v3 consolidates these functions into a consistent interface. Now, operations such as Sign, Verify, Encrypt, Decrypt, and Key generation are each accessible through a unified, builder like API, simplifying integration and enhancing code readability across cryptographic workflows.
However, applications migrating from v2 to v3 will need to update their API calls, as the changes are not backward-compatible. This means that all previous API calls must be rewritten to align with the new, unified API structure. GopenPGP v3 supports the migration process by offering extensive documentation and practical examples. We recommend upgrading to v3 for the latest features and improvements, but we'll continue to support GopenPGP v2 for the time being. Our support includes ongoing bug fixes and minor feature updates to ensure stability and functionality for existing users.
For usage examples of the new API, see the README. For the full documentation, see https://pkg.go.dev/github.com/ProtonMail/gopenpgp/v3.
Profiles
GopenPGP v3 introduces the concept of profiles, enabling applications to configure OpenPGP algorithm selection based on their specific needs. For most applications, the provided preset profiles offer robust and secure defaults, eliminating the need for additional configuration.
RFC 9580 and Interoperability
GopenPGP v3 adds full support for the latest OpenPGP specification, RFC 9580. Compliance with the specification has also been significantly enhanced, as confirmed by the results in the OpenPGP interoperability test suite. These enhancements in GopenPGP v3 are possible by leveraging a new API in the go-crypto fork, which enables a range of improvements in functionality, compliance, and performance.
Go Mobile Support
GopenPGP v3 aims to be fully compatible with Gomobile to provide an API for mobile platforms. For this reason, the library defaults to a builder-like pattern, which is less commonly used in Go. All code that is only relevant for mobile platforms has been moved to the
mobilemodule.Extending Functionality
GopenPGP v3 introduces a streaming interface across all APIs, enabling memory efficient processing of large data.
Additionally, it extends the library's functionality with various improvements, such as:
Full Changelog: ProtonMail/gopenpgp@v2.7.5...v3.0.0.
Changelog since v3.0.0-beta.0: ProtonMail/gopenpgp@v3.0.0-beta.0...v3.0.0.
v2.9.0Compare Source
What's Changed
Changed
v1.3.0.1.22.0.Full Changelog: ProtonMail/gopenpgp@v2.8.3...v2.9.0
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)
v1.38.0Compare Source
Module Highlights
github.com/aws/aws-sdk-go-v2/service/ecr: v1.38.0github.lovev.site/aws/aws-sdk-go-v2/service/ecrpublic: v1.29.0v1.37.2Compare Source
v1.37.1Compare Source
Module Highlights
github.com/aws/aws-sdk-go-v2/service/appstream: v1.47.1Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.