Skip to content

chore: Start SDK semantic versioning from v1#362

Merged
erezrokah merged 1 commit intomainfrom
feat/update_sdk_to_v1
Nov 7, 2022
Merged

chore: Start SDK semantic versioning from v1#362
erezrokah merged 1 commit intomainfrom
feat/update_sdk_to_v1

Conversation

@yevgenypats
Copy link
Copy Markdown
Contributor

This doesn't really break anything but it starts versioning the sdk appropriately so it will be easier to update all plugins once we change to v2 because this change will require us to update everything to /v1 (just search and replace, as no functionally/API changes )

@yevgenypats yevgenypats force-pushed the feat/update_sdk_to_v1 branch from 22db6cb to 6d4d322 Compare November 7, 2022 11:44
@erezrokah erezrokah merged commit 40041c8 into main Nov 7, 2022
@erezrokah erezrokah deleted the feat/update_sdk_to_v1 branch November 7, 2022 11:55
kodiakhq bot pushed a commit that referenced this pull request Nov 7, 2022
🤖 I have created a release *beep* *boop*
---


## [1.0.0](v0.13.23...v1.0.0) (2022-11-07)


### Bug Fixes

* Dont use reflection in reverse transformer ([#360](#360)) ([9c85c1a](9c85c1a))


### Miscellaneous Chores

* Start SDK semantic versioning from v1 ([#362](#362)) ([40041c8](40041c8))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
hermanschaaf added a commit that referenced this pull request Nov 7, 2022
kodiakhq bot pushed a commit that referenced this pull request Nov 7, 2022
Reverts #362

I think the change to use v1 is invalid, as Go expects versioning to be used only from v2 onwards. When importing it in `cloudquery/cloudquery`, I'm getting this error:

```
require github.com/cloudquery/plugin-sdk/v1: version "v1.0.1" invalid: malformed module path "github.com/cloudquery/plugin-sdk/v1"
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants