search

Opteo / google-ads-api

Google Ads API client library for Node.js
https://opteo.com
MIT License
270 stars 90 forks source link

Ads API v12 #443

Closed Zikoel closed 1 year ago

Zikoel commented 1 year ago

Hi guys,

There are plans to release v12 of the library? I saw some work a couple of month ago but no more update! The sunset date for the V11 is fixed at March 31, 2023 and is very close.

rosslavery commented 1 year ago

The latest release is already targeting v12 of the Ads API.

v13 is out now. I tried prepping a PR but unfortunately I'm hitting a blocker. I pinged Opteo just waiting on a response.

wcoots commented 1 year ago

on it today

bharatwaaj commented 1 year ago

What is the timeframe on this upgrade? Can we get to know on a timeline?

wcoots commented 1 year ago

@Zikoel @rosslavery @bharatwaaj Running into some problems compiling the latest proto files. Have contacted Google to see how they can be resolved, but the only timeline I can give is "coming soon".

rosslavery commented 1 year ago

Thanks for the update @wcoots :D

KristijanS99 commented 1 year ago

I just checked on our end it seems v11 is still used, considering v11 lifetime is ending tomorrow is there any updates regarding this? Anything we can do to help guys?

rosslavery commented 1 year ago

The title of this issue is wrong, this library supports V12 in it's current release. The discussion is about getting it updated to support V13.

So if you're up to date with the package, you're fine until September (I believe?).

On Thu, Mar 30, 2023, 5:55 a.m. Kristijan Stefanoski < @.***> wrote:

I just checked on our end it seems v11 is still used, considering v11 lifetime is ending tomorrow is there any updates regarding this? Anything we can do to help guys?

— Reply to this email directly, view it on GitHub https://github.com/Opteo/google-ads-api/issues/443#issuecomment-1490021263, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFAL5GAPTZUWUMLVD5QIHLW6VJ7HANCNFSM6AAAAAAVJJQNFU . You are receiving this because you were mentioned.Message ID: @.***>

Zikoel commented 1 year ago

Sorry to all. There is a desync between the released version on npm currently at version 12.0.1 and the releases decalred on the repo actually at version 11 see.

release

So there is no problem with V12 I will close the issue! Sorry for the noise.