Release tags not matching source? #1617
Description
I am investigating an issue using Data Loader v64.0.2.
During the investigation, I uncovered inconsistencies between the release tags applied to the source code and the actual code used in the release.
This stack trace from v64.0.2 logs reveals the problem:
2025-07-15 09:58:04,923 INFO [main] action.OperationInfoUIHelper instantiateWizard (OperationInfoUIHelper.java:113) - Instantiating wizard: extract
2025-07-15 09:58:09,519 INFO [Thread-2] oauth.OAuthFlowHandler handleOAuthLogin (OAuthFlowHandler.java:71) - Starting OAuth flow
2025-07-15 09:58:09,519 INFO [Thread-2] oauth.OAuthFlowHandler handleOAuthLogin (OAuthFlowHandler.java:84) - Checking if PKCE flow is enabled in Connected App...
2025-07-15 09:58:09,805 INFO [Thread-2] oauth.OAuthFlowHandler isPkceFlowEnabled (OAuthFlowHandler.java:298) - PKCE pre-flight error response: {"error":"invalid_grant","error_description":"invalid authorization code"}
2025-07-15 09:58:09,810 INFO [Thread-2] oauth.OAuthFlowHandler isPkceFlowEnabled (OAuthFlowHandler.java:300) - PKCE pre-flight full response:
2025-07-15 09:58:09,810 WARN [Thread-2] oauth.OAuthFlowHandler isFlowEnabledFromError (OAuthFlowHandler.java:401) - OAuth flow pre-flight check received 'invalid_grant: invalid authorization code'. This may indicate missing OAuth scope (e.g., refresh_token) or other misconfiguration in the Connected App.
Viewing the Code in Github, tag 64.0.2, for the file "src/main/java/com/salesforce/dataloader/oauth/OAuthFlowHandler.java" line 401 reveals that no such logging statement is present!
It appears this line was present in Commit 214b006, but not actually in 64.0.2.
From the looks of it, I think the bug I was investigating would actually be fixed if the source code tagged by 64.0.2 was actually used to build the release, but that doesn't seem to be the case?
I think the Data Loader release/tagging process might need to be scrutinized.
Thanks!