continuous-delivery-scripts 3.5.0__tar.gz → 3.5.1__tar.gz

{continuous_delivery_scripts-3.5.0/continuous_delivery_scripts.egg-info → continuous_delivery_scripts-3.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: continuous-delivery-scripts
-Version: 3.5.0
+Version: 3.5.1
 Summary: Continuous Delivery scripts to increase automation
 Home-page: https://github.com/ARMmbed/continuous-delivery-scripts
 Author: CMSIS team
@@ -141,6 +141,16 @@ Therefore, it installs the following tools which can be used anywhere within a p
 * `cd-generate-spdx`: Generates SPDX documents for the project (3rd party IP reporting/ OpenChain)
 * `cd-license-files`: Updates the Licence header and copyright to all the source code files
 
+For GitHub automation that performs authenticated clone or fetch operations, see [GitHub Token Authentication](#github-token-authentication).
+
+## GitHub Token Authentication
+
+When git operations need to retry against GitHub over HTTPS, this project now uses the credential layout `https://x-access-token:<token>@github.com/<owner>/<repo>.git`.
+
+This means the token is sent in the password position with `x-access-token` as the username, which is the format GitHub accepts for workflow-generated and other non-OAuth tokens used by automation.
+
+Older `https://<token>:x-oauth-basic@github.com/...` URLs were tied to OAuth-style credentials and could reject tokens created dynamically during CI/CD flows.
+
 ## Project Structure
 
 The follow described the major aspects of the project structure:

{continuous_delivery_scripts-3.5.0 → continuous_delivery_scripts-3.5.1}/README.md

@@ -88,6 +88,16 @@ Therefore, it installs the following tools which can be used anywhere within a p
 * `cd-generate-spdx`: Generates SPDX documents for the project (3rd party IP reporting/ OpenChain)
 * `cd-license-files`: Updates the Licence header and copyright to all the source code files
 
+For GitHub automation that performs authenticated clone or fetch operations, see [GitHub Token Authentication](#github-token-authentication).
+
+## GitHub Token Authentication
+
+When git operations need to retry against GitHub over HTTPS, this project now uses the credential layout `https://x-access-token:<token>@github.com/<owner>/<repo>.git`.
+
+This means the token is sent in the password position with `x-access-token` as the username, which is the format GitHub accepts for workflow-generated and other non-OAuth tokens used by automation.
+
+Older `https://<token>:x-oauth-basic@github.com/...` URLs were tied to OAuth-style credentials and could reject tokens created dynamically during CI/CD flows.
+
 ## Project Structure
 
 The follow described the major aspects of the project structure:

{continuous_delivery_scripts-3.5.0 → continuous_delivery_scripts-3.5.1}/continuous_delivery_scripts/_version.py

@@ -11,8 +11,8 @@ References
 This file is autogenerated, do not modify by hand.
 """
 
-__version__ = "3.5.0"
-COMMIT = "c8bbe64d754ac6d58403d50c46679ccebc5e1ef8"
+__version__ = "3.5.1"
+COMMIT = "5f0dc45967d1e56a6e03168c0c9b54cc7aaa98c7"
 MAJOR = 3
 MINOR = 5
-PATCH = 0
+PATCH = 1

{continuous_delivery_scripts-3.5.0 → continuous_delivery_scripts-3.5.1}/continuous_delivery_scripts/utils/git_helpers.py

@@ -39,14 +39,17 @@ class GitWrapper:
     def _git_url_ssh_to_https(self, url: str) -> str:
         """Changes repository URL to use authorisation token.
 
-        Converts the git url to use the GitHub token:
-        See https://github.blog/2012-09-21-easier-builds-and-deployments-using-git-over-https-and-oauth/
+        Converts the git url to use GitHub's token-based HTTPS authentication
+        format so workflow-generated tokens can be used for git operations.
+
+        Reference:
+        https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats
 
         Returns:
             new URL
         """
         path = url.split("github.com", 1)[1][1:].strip()
-        new = "https://{GITHUB_TOKEN}:x-oauth-basic@github.com/%s" % path
+        new = "https://x-access-token:{GITHUB_TOKEN}@github.com/%s" % path
         logger.info("rewriting git url to: %s" % new)
         return new.format(GITHUB_TOKEN=configuration.get_value(ConfigurationVariable.GIT_TOKEN))
 

{continuous_delivery_scripts-3.5.0 → continuous_delivery_scripts-3.5.1/continuous_delivery_scripts.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: continuous-delivery-scripts
-Version: 3.5.0
+Version: 3.5.1
 Summary: Continuous Delivery scripts to increase automation
 Home-page: https://github.com/ARMmbed/continuous-delivery-scripts
 Author: CMSIS team
@@ -141,6 +141,16 @@ Therefore, it installs the following tools which can be used anywhere within a p
 * `cd-generate-spdx`: Generates SPDX documents for the project (3rd party IP reporting/ OpenChain)
 * `cd-license-files`: Updates the Licence header and copyright to all the source code files
 
+For GitHub automation that performs authenticated clone or fetch operations, see [GitHub Token Authentication](#github-token-authentication).
+
+## GitHub Token Authentication
+
+When git operations need to retry against GitHub over HTTPS, this project now uses the credential layout `https://x-access-token:<token>@github.com/<owner>/<repo>.git`.
+
+This means the token is sent in the password position with `x-access-token` as the username, which is the format GitHub accepts for workflow-generated and other non-OAuth tokens used by automation.
+
+Older `https://<token>:x-oauth-basic@github.com/...` URLs were tied to OAuth-style credentials and could reject tokens created dynamically during CI/CD flows.
+
 ## Project Structure
 
 The follow described the major aspects of the project structure: