Skip to content

meta: add back engines#85

Closed
larsgw wants to merge 1 commit intonpm:release-nextfrom
larsgw:patch-5
Closed

meta: add back engines#85
larsgw wants to merge 1 commit intonpm:release-nextfrom
larsgw:patch-5

Conversation

@larsgw
Copy link
Copy Markdown
Contributor

@larsgw larsgw commented Oct 23, 2018

Add back engine restrictions, as npm 6 is incompatible with node 4 but still tries to update.

See https://npm.community/t/2837
See c6ddb64

Add back engine restrictions, as npm 6 is incompatible with node 4 but 
still tries to update.

See https://npm.community/t/2837
See c6ddb64
@larsgw larsgw requested a review from a team as a code owner October 23, 2018 11:59
@zkat
Copy link
Copy Markdown
Contributor

zkat commented Nov 13, 2018

We have a separate mechanism for notifying users of incompatibility. I do not consider this to be necessary and, as pointed out, causes pains when testing npm itself.

@zkat zkat closed this Nov 13, 2018
Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
* feat: multi-account support with --account flag, per-account credential storage

- Add --account global flag and GOOGLE_WORKSPACE_CLI_ACCOUNT env var
- Per-account encrypted credential files (credentials.<b64-email>.enc)
- Per-account token cache (token_cache.<b64-email>.json)
- accounts.json registry with default account tracking
- New auth subcommands: list, default, per-account logout
- login_hint in OAuth URL for account pre-selection
- Email validation via Google userinfo after OAuth flow
- 12 new unit tests (380 total)

BREAKING CHANGE: Existing users must run 'gws auth login' again.
Credential storage changed from single credentials.enc to per-account files.

* refactor: Improve error handling for file system operations, rename `GWS_ACCOUNT` to `GOOGLE_WORKSPACE_CLI_ACCOUNT`, and refine service account token cache path generation.

* fix: clean up per-account token caches on logout

---------

Co-authored-by: jpoehnelt-bot <jpoehnelt-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants