Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 3 commits
- 12 files changed
- 2 contributors
Commits on May 29, 2025
-
chore(deps): Update module github.com/cloudquery/plugin-sdk/v4 to v4.…
…83.0 (#2178) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/cloudquery/plugin-sdk/v4](https://redirect.github.com/cloudquery/plugin-sdk) | require | minor | `v4.82.2` -> `v4.83.0` | --- ### Release Notes <details> <summary>cloudquery/plugin-sdk (github.com/cloudquery/plugin-sdk/v4)</summary> ### [`v4.83.0`](https://redirect.github.com/cloudquery/plugin-sdk/releases/tag/v4.83.0) [Compare Source](https://redirect.github.com/cloudquery/plugin-sdk/compare/v4.82.2...v4.83.0) ##### Features - Switch state grpc client to NewClient rather than DialContext ([#​2176](https://redirect.github.com/cloudquery/plugin-sdk/issues/2176)) ([9356d9d](https://redirect.github.com/cloudquery/plugin-sdk/commit/9356d9d14f89d3c1ea58848ae3e53d671f5b4c8f)) ##### Bug Fixes - **deps:** Update dependency go to v1.24.3 ([#​2041](https://redirect.github.com/cloudquery/plugin-sdk/issues/2041)) ([c438d69](https://redirect.github.com/cloudquery/plugin-sdk/commit/c438d690057cb2b8fb4944a5108b0c9bd5bfe294)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4yMi4xIiwidXBkYXRlZEluVmVyIjoiNDAuMjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYXV0b21lcmdlIl19-->
Commits on May 30, 2025
-
feat: Make SDK FIPS-compliant by using internal SHA1 module (#2179)
The Go standard library has removed support for using SHA1 when in FIPS mode in golang/go@54693a8. However the [NIST FIPS spec](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar1.pdf) allows for using SHA1 in certain cases: > SHA-1 for non-digital signature applications: > For all other hash function applications, the use of SHA-1 is **acceptable**. The other > applications include HMAC, Key Derivation Functions (KDFs), Random Bit Generation, and > hash-only applications (e.g., hashing passwords and using SHA-1 to compute a checksum, > such as the approved integrity technique specified in Section 4.6.1 of [FIPS 140]). The above removal from the standard lib is too restrictive, as we should be able to use this algo in our SDK for checksums. I've borrowed the implementation of packages `sha1` and `byteorder` and added them as internal modules.
-
chore(main): Release v4.84.0 (#2180)
🤖 I have created a release *beep* *boop* --- ## [4.84.0](v4.83.0...v4.84.0) (2025-05-30) ### Features * Make SDK FIPS-compliant by using internal SHA1 module ([#2179](#2179)) ([5a34e35](5a34e35)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.83.0...v4.84.0