You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,6 +104,33 @@ Follow these steps to make a contribution to the project:
104
104
```
105
105
- Create a GitHub pull request, selecting `main` as the target branch
106
106
107
+
## Releases
108
+
109
+
### Manual Release
110
+
Releases must be triggered manually by an approver. This can be done either via `GitHub Actions` (workflow dispatch) or through the `GitHub Releases` page using the **Draft a new release** option. The *Release Manual* workflow is responsible for creating and completing the release.
111
+
112
+
Option 1: Release via Workflow Dispatch
113
+
114
+
- Go to Actions and select the *Release Manual* workflow.
115
+
116
+
- Click **Run workflow**.
117
+
118
+
- Enter the next incremented version number with the v prefix (for example, v1.2.3).
119
+
120
+
- The workflow will create the release and upload the build artifacts once completed.
121
+
122
+
Option 2: Release via Draft Release
123
+
124
+
- Go to Releases and click **Draft a new release**.
125
+
126
+
- Create a new tag using the next incremented version with the v prefix.
127
+
128
+
- Fill in the release title and description.
129
+
130
+
- Click Publish release.
131
+
132
+
- The release will appear immediately on the Releases page. This action will also trigger the *Release Manual* workflow, which will build the artifacts and upload them to the published release once the workflow finishes.
133
+
107
134
108
135
## Notes
109
136
These commit IDs represent the last migration checkpoint from each provider's original repository, marking the final commit that was copied during the consolidation process.
"json_key": "<string> (required if credentials_source = 'static')",
19
+
"storage_class": "<string> (optional - default: 'STANDARD', check for more options=https://docs.cloud.google.com/storage/docs/storage-classes)",
20
+
"encryption_key": "<string> (optional)",
21
+
}
22
+
```
23
+
24
+
### Credentials Source Types
25
+
***"":** specifies that credentials should be detected. Application Default Credentials will be used if avaliable. A read-only client will be used otherwise.
26
+
***"none":** specifies that credentials are explicitly empty and that the client should be restricted to a read-only scope.
27
+
***"static:"** specifies that a service account file included in json_key should be used for authentication.
14
28
15
29
### Authentication Methods (`credentials_source`)
16
30
*`static`: A [service account](https://cloud.google.com/iam/docs/creating-managing-service-account-keys) key will be provided via the `json_key` field.
0 commit comments