upgrading golang-google-api-dev: how much caution is needed?

To: debian-go@lists.debian.org
Subject: upgrading golang-google-api-dev: how much caution is needed?
From: Drew Parsons <dparsons@debian.org>
Date: Mon, 28 Sep 2020 14:05:59 +0800
Message-id: <[🔎] 2e0ac1e384b339812da10270046182e1@debian.org>
Reply-to: dparsons@debian.org

The latest version of rclone requires golang-google-api-dev 0.28 [1].Current version is 0.21.


How sensitive is the go ecosystem to golang-google-api-dev version?

Should we take care to be careful, and upgrade in experimental first?

Or just push google-api 0.28 straight into unstable?

Drew

[1] specifically, rclone needs the api upgrade to definedrive/v3.FileShortcutDetails, used in rclone/backend/drive

Reply to:

Follow-Ups:
- Re: upgrading golang-google-api-dev: how much caution is needed?
  - From: Shengjing Zhu <zhsj@debian.org>

Prev by Date: Bug#971078: RFP: golang-storj-io-uplink -- Go library for Storj V3 Network
Next by Date: announcement: go-md2man-v2 uploaded to NEW queue
Previous by thread: Bug#971078: RFP: golang-storj-io-uplink -- Go library for Storj V3 Network
Next by thread: Re: upgrading golang-google-api-dev: how much caution is needed?
Index(es):
- Date
- Thread