[GODRIVER-2151] Retract Go Driver v1.6.0-v1.6.1 and v1.7.0-v1.7.1 Created: 07/Sep/21  Updated: 18/Oct/21  Resolved: 18/Oct/21

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.8.0

Type: Task Priority: Critical - P2
Reporter: Matt Dale Assignee: Benji Rewis (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GODRIVER-2109 Race condition in staleness checks if... Closed
Documentation Changes: Not Needed

 Description   

Retract Go Driver v1.6.0-v1.6.1 and v1.7.0-v1.7.1 which are affected by the bug in GODRIVER-2109 using a retract directive in the go.mod file.

Example:

retract (
	[v1.6.0, v1.6.1] // Contains data race bug in background connection establishment.
	[v1.7.0, v1.7.1] // Contains data race bug in background connection establishment.
)



 Comments   
Comment by Benji Rewis (Inactive) [ 18/Oct/21 ]

Retracted with the retract directive.

Comment by Githook User [ 18/Oct/21 ]

Author:

{'name': 'Benjamin Rewis', 'email': '32186188+benjirewis@users.noreply.github.com', 'username': 'benjirewis'}

Message: GODRIVER-2151 Retract v1.6.0-v1.6.1 and v1.7.0-v1.7.1 (#758)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/cdcce6324dc605ee842a2d37bbee4adecac68e9f

Comment by Benji Rewis (Inactive) [ 28/Sep/21 ]

Using a retract directive throws an error when building with Golang versions < 1.16. So, we'll have to file for a request to remove the packages manually. Here's an issue.

Comment by Alexej Kubarev [ 08/Sep/21 ]

FYI: It's possible to release 1.7.3 that has zero changes and only contains retraction additions:

retract (	
  [v1.6.0, v1.6.1] // Contains data race bug in background connection establishment.	
  [v1.7.0, v1.7.1] // Contains data race bug in background connection establishment.
  v1.7.3 // Only contains retractions for previous versions with data races
)

The net-effect would be that a user performing go get of @latest would find 1.7.3 (as latest version) and read retractions, and thus only fetch 1.7.2 version.

Retraction should be done as early as possible and not await for a standard release cycles to avoid problems and help clients update/downgrade to correct versions.

Generated at Thu Feb 08 08:37:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.