-
Notifications
You must be signed in to change notification settings - Fork 547
Comparing changes
Open a pull request
base repository: cloudquery/cloudquery
base: v6.20.0
head repository: cloudquery/cloudquery
compare: v6.20.1
- 8 commits
- 88 files changed
- 4 contributors
Commits on May 19, 2025
-
fix(deps): Update module github.com/cloudquery/plugin-sdk/v4 to v4.80…
….3 (#20802) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/cloudquery/plugin-sdk/v4](https://redirect.github.com/cloudquery/plugin-sdk) | require | patch | `v4.80.2` -> `v4.80.3` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>cloudquery/plugin-sdk (github.com/cloudquery/plugin-sdk/v4)</summary> ### [`v4.80.3`](https://redirect.github.com/cloudquery/plugin-sdk/releases/tag/v4.80.3) [Compare Source](https://redirect.github.com/cloudquery/plugin-sdk/compare/v4.80.2...v4.80.3) ##### Bug Fixes - Pass correct value for plugin version ([#​2156](https://redirect.github.com/cloudquery/plugin-sdk/issues/2156)) ([37b4157](https://redirect.github.com/cloudquery/plugin-sdk/commit/37b41572165f96c8d0c67390bded2b20815a506d)) </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. --- - [ ] 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).
Configuration menu - View commit details
-
Copy full SHA for 2ba2f8e - Browse repository at this point
Copy the full SHA 2ba2f8eView commit details -
fix(deps): Update module github.com/cloudquery/cloudquery/cli/v6 to v…
…6.20.0 (#20805) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/cloudquery/cloudquery/cli/v6](https://redirect.github.com/cloudquery/cloudquery) | require | minor | `v6.19.2` -> `v6.20.0` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>cloudquery/cloudquery (github.com/cloudquery/cloudquery/cli/v6)</summary> ### [`v6.20.0`](https://redirect.github.com/cloudquery/cloudquery/releases/tag/cli-v6.20.0) [Compare Source](https://redirect.github.com/cloudquery/cloudquery/compare/v6.19.2...v6.20.0) ##### Features - Add 'auto_obfuscate' transformation to basic transformer ([#​20728](https://redirect.github.com/cloudquery/cloudquery/issues/20728)) ([66cbf0a](https://redirect.github.com/cloudquery/cloudquery/commit/66cbf0a36ed751481f6d61417777150a24f312a6)) ##### Bug Fixes - **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.80.2 ([#​20778](https://redirect.github.com/cloudquery/cloudquery/issues/20778)) ([525352c](https://redirect.github.com/cloudquery/cloudquery/commit/525352c3d5ce3dd258358b7396b2cebd6ae3ce87)) </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. --- - [ ] 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).
Configuration menu - View commit details
-
Copy full SHA for bf9ac6c - Browse repository at this point
Copy the full SHA bf9ac6cView commit details
Commits on May 20, 2025
-
feat!: Add DeleteRecord handling to Clickhouse destination (#20772)
This adds handling for `DeleteRecord` messages in ClickHouse along with tests. I've also enabled the `DeleteRecord` tests in Postgres as they were excluded by mistake.
Configuration menu - View commit details
-
Copy full SHA for 13e9573 - Browse repository at this point
Copy the full SHA 13e9573View commit details -
chore(main): Release plugins-destination-clickhouse v7.0.0 (#20781)
🤖 I have created a release *beep* *boop* --- ## [7.0.0](plugins-destination-clickhouse-v6.2.7...plugins-destination-clickhouse-v7.0.0) (2025-05-20) ### ⚠ BREAKING CHANGES * Add DeleteRecord handling to Clickhouse destination ([#20772](#20772)) ### Features * Add DeleteRecord handling to Clickhouse destination ([#20772](#20772)) ([13e9573](13e9573)) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.80.2 ([#20778](#20778)) ([525352c](525352c)) * **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.80.3 ([#20802](#20802)) ([2ba2f8e](2ba2f8e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Configuration menu - View commit details
-
Copy full SHA for 4f1cc2a - Browse repository at this point
Copy the full SHA 4f1cc2aView commit details -
chore: Update ClickHouse docs with min supported version (#20807)
A small oversight in #20772.
Configuration menu - View commit details
-
Copy full SHA for 5054bdd - Browse repository at this point
Copy the full SHA 5054bddView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4ee5982 - Browse repository at this point
Copy the full SHA 4ee5982View commit details -
fix: Timestamp field replacement (#20809)
#### Summary We've seen a panic on our Cloud syncs when syncing from ClickHouse to BigQuery, the panic is ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0xf9bd50] goroutine 138 [running]: github.com/cloudquery/plugin-sdk/v4/schema.ReplaceFieldInRecord({0x0, 0x0}, {0x15ff4f5, 0xf}, {0x182bda0, 0xc0003844b0}) /home/runner/go/pkg/mod/github.com/cloudquery/plugin-sdk/v4@v4.79.1/schema/arrow.go:99 +0x30 github.com/cloudquery/cloudquery/cli/v6/internal/transformer.(*RecordTransformer).Transform(0xc0005c29c0, {0x182a050, 0xc0007d0720}) /home/runner/work/cloudquery/cloudquery/cli/internal/transformer/transformer.go:154 +0x46d github.com/cloudquery/cloudquery/cli/v6/cmd.syncConnectionV3.func6() /home/runner/work/cloudquery/cloudquery/cli/cmd/sync_v3.go:494 +0xc15 golang.org/x/sync/errgroup.(*Group).Go.func1() /home/runner/go/pkg/mod/golang.org/x/sync@v0.13.0/errgroup/errgroup.go:79 +0x50 created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 1 /home/runner/go/pkg/mod/golang.org/x/sync@v0.13.0/errgroup/errgroup.go:76 +0x93 {"severity":"info","module":"launcher","timestamp":"2025-05-19T00:15:07.413712727Z","message":"post-flight checks passed"} Sync run completed with status 2 ``` The issue was that the schema of the source sync time column didn't not have the timezone (was an empty string) so when we tried to replace it with a UTC timezone `schema.ReplaceFieldInRecord` failed due to type mismatch returning a `nil` record.Configuration menu - View commit details
-
Copy full SHA for ee81ce9 - Browse repository at this point
Copy the full SHA ee81ce9View commit details -
chore(main): Release cli v6.20.1 (#20804)
🤖 I have created a release *beep* *boop* --- ## [6.20.1](cli-v6.20.0...cli-v6.20.1) (2025-05-20) ### Bug Fixes * **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.80.3 ([#20802](#20802)) ([2ba2f8e](2ba2f8e)) * Timestamp field replacement ([#20809](#20809)) ([ee81ce9](ee81ce9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Configuration menu - View commit details
-
Copy full SHA for 164f75d - Browse repository at this point
Copy the full SHA 164f75dView commit details
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 v6.20.0...v6.20.1