…80.1 (#2152)

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.0` -> `v4.80.1` |

---

### Release Notes

<details>
<summary>cloudquery/plugin-sdk (github.com/cloudquery/plugin-sdk/v4)</summary>

### [`v4.80.1`](https://redirect.github.com/cloudquery/plugin-sdk/releases/tag/v4.80.1)

[Compare Source](https://redirect.github.com/cloudquery/plugin-sdk/compare/v4.80.0...v4.80.1)

##### Bug Fixes

-   **deps:** Update module github.com/cloudquery/codegen to v0.3.27 ([#&#8203;2148](https://redirect.github.com/cloudquery/plugin-sdk/issues/2148)) ([1fd7b1e](https://redirect.github.com/cloudquery/plugin-sdk/commit/1fd7b1e95a262017152616290da791e08fc497b8))
-   **deps:** Update module github.com/cloudquery/codegen to v0.3.28 ([#&#8203;2150](https://redirect.github.com/cloudquery/plugin-sdk/issues/2150)) ([4d1409c](https://redirect.github.com/cloudquery/plugin-sdk/commit/4d1409c402fd5e8b793ee0586e9d2ec8c3812cd5))
-   **deps:** Update module github.com/cloudquery/plugin-pb-go to v1.26.11 ([#&#8203;2149](https://redirect.github.com/cloudquery/plugin-sdk/issues/2149)) ([a904b46](https://redirect.github.com/cloudquery/plugin-sdk/commit/a904b461a5ca7eebb0c6f4c807db9aa23011a2b5))
-   **deps:** Update module github.com/samber/lo to v1.49.1 ([#&#8203;2139](https://redirect.github.com/cloudquery/plugin-sdk/issues/2139)) ([f11b5e6](https://redirect.github.com/cloudquery/plugin-sdk/commit/f11b5e67d95af1f54410236bbefb071c01c5df82))

</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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWVyZ2UiXX0=-->

The current logic for `BatchWriter` does not flush `DeleteRecord` messages when the writer is flushed. This PR adds that flushing.

I'm also wondering whether we should add a call to `flushDeleteRecordTables` in https://github.com/cloudquery/plugin-sdk/blob/main/writers/batchwriter/batchwriter.go#L307-L315. WDYT?

…ed, not exceeded (#2153)

The current logic for batch writing prevents us from cleanly testing the `DeleteRecord` handling in the plugin. Currently we have to set `BatchSize: 1` and send two `DeleteRecord` messages in the test, which is not the cleanest logic. This PR changes the logic so the batch is flushed when the batch size is reached, not exceeded (so for `BatchSize: 1` it will flush after one `DeleteRecord` is received).

This also matches the logic we have in https://github.com/cloudquery/plugin-sdk/blob/main/internal/batch/cap.go#L7.

🤖 I have created a release *beep* *boop*
---


## [4.80.2](v4.80.1...v4.80.2) (2025-05-19)


### Bug Fixes

* Change logic for batch writing to write when batch size is reached, not exceeded ([#2153](#2153)) ([58c8a1e](58c8a1e))
* Flush DeleteRecord messages when batch writer is flushed ([#2154](#2154)) ([791c865](791c865))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).