chore: release versions (#351)

This commit is contained in:
googleworkspace-bot
2026-03-10 12:30:44 -06:00
committed by GitHub
parent 80fd6c51ea
commit 58c412c768
9 changed files with 18 additions and 30 deletions
-5
View File
@@ -1,5 +0,0 @@
---
"@googleworkspace/cli": patch
---
fix(auth): dynamically fetch scopes from Discovery docs when `-s` specifies services not in static scope lists
-5
View File
@@ -1,5 +0,0 @@
---
"@googleworkspace/cli": patch
---
fix(auth): format extract_scopes_from_doc and deduplicate dynamic scopes
-5
View File
@@ -1,5 +0,0 @@
---
"@googleworkspace/cli": patch
---
Bring `+forward` behavior in line with Gmail's web UI: keep the forward in the sender's original thread, add a blank line between the forwarded message metadata and body, and remove the spurious closing delimiter.
-5
View File
@@ -1,5 +0,0 @@
---
"@googleworkspace/cli": patch
---
Fix gmail +triage 403 error by using gmail.readonly scope instead of gmail.modify to avoid conflict with gmail.metadata scope that does not support the q parameter
-5
View File
@@ -1,5 +0,0 @@
---
"@googleworkspace/cli": minor
---
Add `GOOGLE_WORKSPACE_CLI_KEYRING_BACKEND` env var for explicit keyring backend selection (`keyring` or `file`). Fixes credential key loss in Docker/keyring-less environments by never deleting `.encryption_key` and always persisting it as a fallback.
+13
View File
@@ -1,5 +1,18 @@
# @googleworkspace/cli
## 0.10.0
### Minor Changes
- 8d89325: Add `GOOGLE_WORKSPACE_CLI_KEYRING_BACKEND` env var for explicit keyring backend selection (`keyring` or `file`). Fixes credential key loss in Docker/keyring-less environments by never deleting `.encryption_key` and always persisting it as a fallback.
### Patch Changes
- 06aa698: fix(auth): dynamically fetch scopes from Discovery docs when `-s` specifies services not in static scope lists
- 06aa698: fix(auth): format extract_scopes_from_doc and deduplicate dynamic scopes
- 5e7d120: Bring `+forward` behavior in line with Gmail's web UI: keep the forward in the sender's original thread, add a blank line between the forwarded message metadata and body, and remove the spurious closing delimiter.
- 2782cf1: Fix gmail +triage 403 error by using gmail.readonly scope instead of gmail.modify to avoid conflict with gmail.metadata scope that does not support the q parameter
## 0.9.1
### Patch Changes
Generated
+3 -3
View File
@@ -845,7 +845,7 @@ dependencies = [
[[package]]
name = "gws"
version = "0.9.1"
version = "0.10.0"
dependencies = [
"aes-gcm",
"anyhow",
@@ -2150,9 +2150,9 @@ dependencies = [
[[package]]
name = "schannel"
version = "0.1.28"
version = "0.1.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "891d81b926048e76efe18581bf793546b4c0eaf8448d72be8de2bbee5fd166e1"
checksum = "91c1b7e4904c873ef0710c1f407dde2e6287de2bebc1bbbf7d430bb7cbffd939"
dependencies = [
"windows-sys 0.61.2",
]
+1 -1
View File
@@ -14,7 +14,7 @@
[package]
name = "gws"
version = "0.9.1"
version = "0.10.0"
edition = "2021"
description = "Google Workspace CLI — dynamic command surface from Discovery Service"
license = "Apache-2.0"
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@googleworkspace/cli",
"version": "0.9.1",
"version": "0.10.0",
"private": true,
"description": "Google Workspace CLI — dynamic command surface from Discovery Service",
"license": "Apache-2.0",