Skip to content

Commit

Permalink
feat: Automated regeneration of chromemanagement v1 client
Browse files Browse the repository at this point in the history
  • Loading branch information
yoshi-automation committed Feb 28, 2021
1 parent b635f0c commit 4b38716
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 3 deletions.
4 changes: 4 additions & 0 deletions generated/google-apis-chromemanagement_v1/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Release history for google-apis-chromemanagement_v1

### v0.2.0 (2021-02-28)

* Regenerated from discovery document revision 20210227

### v0.1.0 (2021-02-20)

* Regenerated from discovery document revision 20210218
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,9 @@ module ChromemanagementV1
# Version of the Chrome Management API this client connects to.
# This is NOT the gem version.
VERSION = 'V1'

# See reports about devices and Chrome browsers managed within your organization
AUTH_CHROME_MANAGEMENT_REPORTS_READONLY = 'https://www.googleapis.com/auth/chrome.management.reports.readonly'
end
end
end
Original file line number Diff line number Diff line change
Expand Up @@ -16,13 +16,13 @@ module Google
module Apis
module ChromemanagementV1
# Version of the google-apis-chromemanagement_v1 gem
GEM_VERSION = "0.1.0"
GEM_VERSION = "0.2.0"

# Version of the code generator used to generate this client
GENERATOR_VERSION = "0.1.2"

# Revision of the discovery document this client was generated from
REVISION = "20210218"
REVISION = "20210227"
end
end
end
2 changes: 1 addition & 1 deletion generated/google-apis-chromemanagement_v1/synth.metadata
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"git": {
"name": ".",
"remote": "https://github.com/googleapis/google-api-ruby-client.git",
"sha": "4a699594de3ff8eca8d59897485ca7d08e07d193"
"sha": "b635f0c06b806c6461f300f40683f1b8f8127cd0"
}
}
]
Expand Down

0 comments on commit 4b38716

Please sign in to comment.