		@@ -12,3 +12,3 @@ /* Type definitions for non-npm package Cloud Scheduler API v1beta1 0.0 */
		// Generated from: https://cloudscheduler.googleapis.com/$discovery/rest?version=v1beta1
		// Revision: 20230612
		// Revision: 20230630

		@@ -265,10 +265,10 @@ /// <reference types="gapi.client" />
		interface PubsubMessage {
		/** Attributes for this message. If this field is empty, the message must contain non-empty data. This can be used to filter messages on the subscription. */
		/** Optional. Attributes for this message. If this field is empty, the message must contain non-empty data. This can be used to filter messages on the subscription. */
		attributes?:
		{ [P in string]: string };
		/** The message data field. If this field is empty, the message must contain at least one attribute. */
		/** Optional. The message data field. If this field is empty, the message must contain at least one attribute. */
		data?:
		string;
		/**
		* ID of this message, assigned by the server when the message is published. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a
		* Optional. ID of this message, assigned by the server when the message is published. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a
		* `PubsubMessage` via a `Pull` call or a push delivery. It must not be populated by the publisher in a `Publish` call.
		@@ -279,9 +279,9 @@ */
		/**
		* If non-empty, identifies related messages for which publish order should be respected. If a `Subscription` has `enable_message_ordering` set to `true`, messages published with the
		* same non-empty `ordering_key` value will be delivered to subscribers in the order in which they are received by the Pub/Sub system. All `PubsubMessage`s published in a given
		* `PublishRequest` must specify the same `ordering_key` value. For more information, see [ordering messages](https://cloud.google.com/pubsub/docs/ordering).
		* Optional. If non-empty, identifies related messages for which publish order should be respected. If a `Subscription` has `enable_message_ordering` set to `true`, messages published
		* with the same non-empty `ordering_key` value will be delivered to subscribers in the order in which they are received by the Pub/Sub system. All `PubsubMessage`s published in a
		* given `PublishRequest` must specify the same `ordering_key` value. For more information, see [ordering messages](https://cloud.google.com/pubsub/docs/ordering).
		*/
		orderingKey?:
		string;
		/** The time at which the message was published, populated by the server when it receives the `Publish` call. It must not be populated by the publisher in a `Publish` call. */
		/** Optional. The time at which the message was published, populated by the server when it receives the `Publish` call. It must not be populated by the publisher in a `Publish` call. */
		publishTime?:
		@@ -288,0 +288,0 @@ string;

package.json

		{
		"name": "@maxim_mazurok/gapi.client.cloudscheduler-v1beta1",
		"version": "0.0.20230612",
		"version": "0.0.20230630",
		"description": "TypeScript typings for Cloud Scheduler API v1beta1",
		@@ -5,0 +5,0 @@ "license": "MIT",

tests.ts

		@@ -6,3 +6,3 @@ /* This is stub file for gapi.client.cloudscheduler-v1beta1 definition tests */

		// Revision: 20230612
		// Revision: 20230630

		@@ -9,0 +9,0 @@ gapi.load('client', async () => {

@maxim_mazurok/gapi.client.cloudscheduler-v1beta1 - npm Package Compare versions

Improved metrics