Skip to content

Commit

Permalink
chore: add api_shortname and library_type to repo metadata (#573)
Browse files Browse the repository at this point in the history
  • Loading branch information
parthea authored Jan 12, 2022
1 parent d502e80 commit 64d7621
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 7 deletions.
6 changes: 4 additions & 2 deletions packages/google-cloud-automl/.repo-metadata.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"distribution_name": "@google-cloud/automl",
"release_level": "ga",
"release_level": "stable",
"product_documentation": "https://cloud.google.com/automl/docs/",
"repo": "googleapis/nodejs-automl",
"default_version": "v1",
Expand All @@ -11,5 +11,7 @@
"name": "automl",
"name_pretty": "Cloud AutoML",
"api_id": "automl.googleapis.com",
"codeowner_team": "@googleapis/ml-apis"
"codeowner_team": "@googleapis/ml-apis",
"api_shortname": "automl",
"library_type": "GAPIC_COMBO"
}
9 changes: 4 additions & 5 deletions packages/google-cloud-automl/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

# [Cloud AutoML: Node.js Client](https://github.com/googleapis/nodejs-automl)

[![release level](https://img.shields.io/badge/release%20level-general%20availability%20%28GA%29-brightgreen.svg?style=flat)](https://cloud.google.com/terms/launch-stages)
[![release level](https://img.shields.io/badge/release%20level-stable-brightgreen.svg?style=flat)](https://cloud.google.com/terms/launch-stages)
[![npm version](https://img.shields.io/npm/v/@google-cloud/automl.svg)](https://www.npmjs.org/package/@google-cloud/automl)


Expand Down Expand Up @@ -179,18 +179,17 @@ _Legacy Node.js versions are supported as a best effort:_
This library follows [Semantic Versioning](http://semver.org/).


This library is considered to be **General Availability (GA)**. This means it
is stable; the code surface will not change in backwards-incompatible ways

This library is considered to be **stable**. The code surface will not change in backwards-incompatible ways
unless absolutely necessary (e.g. because of critical security issues) or with
an extensive deprecation period. Issues and requests against **GA** libraries
an extensive deprecation period. Issues and requests against **stable** libraries
are addressed with the highest priority.







More Information: [Google Cloud Platform Launch Stages][launch_stages]

[launch_stages]: https://cloud.google.com/terms/launch-stages
Expand Down

0 comments on commit 64d7621

Please sign in to comment.