You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: release_blocked field in per-library configuration (#2243)
Fixes#897.
This change implements the "release init" command part
(`release_blocked`).
When library config has release_blocked field set to true, the "release
init" command skips the library processing. If the library ID is
explicitly specified, then `release_blocked` is ignored.
|`id`| string | A unique identifier for the library, in a language-specific format. It should not be empty and only contains alphanumeric characters, slashes, periods, underscores, and hyphens. | Yes | Must be a valid library ID. |
31
31
|`next_version`| string | The next released version of the library. Ignored unless it would increase the release version. | No | Must be a valid semantic version, "v" prefix is optional. |
32
-
|`generate_blocked`| bool | Set this to `true` to skip the generation of this library. It's `false` by default. | No ||
32
+
|`generate_blocked`| bool | (When this library is not explicitlly specified in the `-library` argument) Set this to `true` to skip the generation of this library. It's `false` by default. | No ||
33
+
|`release_blocked`| bool | (When this library is not explicitlly specified in the `-library` argument) Set this to `true` to skip the release of this library. It's `false` by default. | No ||
0 commit comments