From 69eb852d6fc45afb748fc7efd260dd34aa15bcda Mon Sep 17 00:00:00 2001 From: Timothy Johnson Date: Mon, 26 Aug 2024 08:14:38 -0400 Subject: [PATCH 01/14] Update micromatch dependency Signed-off-by: Timothy Johnson --- npm-shrinkwrap.json | 12 ++++++------ packages/cli/CHANGELOG.md | 4 ++++ 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json index 19a68f7d3..9f37436a0 100644 --- a/npm-shrinkwrap.json +++ b/npm-shrinkwrap.json @@ -14629,9 +14629,9 @@ } }, "node_modules/micromatch": { - "version": "4.0.7", - "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.7.tgz", - "integrity": "sha512-LPP/3KorzCwBxfeUuZmaR6bG2kdeHSbe0P2tY3FLRU4vYrjYz5hI4QZwV0njUx3jeuKe67YukQ1LSPZBKDqO/Q==", + "version": "4.0.8", + "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz", + "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==", "dependencies": { "braces": "^3.0.3", "picomatch": "^2.3.1" @@ -32019,9 +32019,9 @@ "integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==" }, "micromatch": { - "version": "4.0.7", - "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.7.tgz", - "integrity": "sha512-LPP/3KorzCwBxfeUuZmaR6bG2kdeHSbe0P2tY3FLRU4vYrjYz5hI4QZwV0njUx3jeuKe67YukQ1LSPZBKDqO/Q==", + "version": "4.0.8", + "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz", + "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==", "requires": { "braces": "^3.0.3", "picomatch": "^2.3.1" diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index e265fbf4e..04bceae29 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -2,6 +2,10 @@ All notable changes to the Zowe CLI package will be documented in this file. +## Recent Changes + +- BugFix: Updated `micromatch` dependency for technical currency. [#2242](https://github.com/zowe/zowe-cli/pull/2242) + ## `7.28.3` - BugFix: Refactored code to reduce the use of deprecated functions to prepare for upcoming Node.js 22 support. [#2191](https://github.com/zowe/zowe-cli/issues/2191) From 93f179a84e979e60619a446ed9a513d16947c3b6 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Mon, 26 Aug 2024 11:23:19 -0400 Subject: [PATCH 02/14] Enable nightly audit Signed-off-by: Andrew W. Harn --- .github/workflows/audit.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/audit.yml b/.github/workflows/audit.yml index 6e5ae56eb..12bd5c949 100644 --- a/.github/workflows/audit.yml +++ b/.github/workflows/audit.yml @@ -6,8 +6,8 @@ on: - master - zowe-v1-lts - next - # schedule: - # - cron: '0 10 * * *' + schedule: + - cron: '0 10 * * *' jobs: audit: From 5bfb95269a2a7072ffdb4c261f1cc98b159bcd0e Mon Sep 17 00:00:00 2001 From: zowe-robot Date: Mon, 26 Aug 2024 16:52:05 +0000 Subject: [PATCH 03/14] Bump version to 7.29.1 [ci skip] Signed-off-by: zowe-robot --- lerna.json | 2 +- npm-shrinkwrap.json | 2 +- packages/cli/CHANGELOG.md | 2 +- packages/cli/package.json | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/lerna.json b/lerna.json index 3a899b9d1..f3e66208c 100644 --- a/lerna.json +++ b/lerna.json @@ -1,5 +1,5 @@ { - "version": "7.29.0", + "version": "7.29.1", "command": { "publish": { "ignoreChanges": [ diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json index 9f37436a0..6f2fb5790 100644 --- a/npm-shrinkwrap.json +++ b/npm-shrinkwrap.json @@ -20222,7 +20222,7 @@ }, "packages/cli": { "name": "@zowe/cli", - "version": "7.29.0", + "version": "7.29.1", "hasInstallScript": true, "license": "EPL-2.0", "dependencies": { diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index 04bceae29..4274f8715 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -2,7 +2,7 @@ All notable changes to the Zowe CLI package will be documented in this file. -## Recent Changes +## `7.29.1` - BugFix: Updated `micromatch` dependency for technical currency. [#2242](https://github.com/zowe/zowe-cli/pull/2242) diff --git a/packages/cli/package.json b/packages/cli/package.json index 5f305773c..d00d7c606 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/cli", - "version": "7.29.0", + "version": "7.29.1", "description": "Zowe CLI is a command line interface (CLI) that provides a simple and streamlined way to interact with IBM z/OS.", "author": "Zowe", "license": "EPL-2.0", From fa2c514c694782efff99aa7f93176a646877204e Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Mon, 26 Aug 2024 15:17:31 -0400 Subject: [PATCH 04/14] Make some changes to contributing Signed-off-by: Andrew W. Harn --- CONTRIBUTING.md | 28 +++- docs/CommandFormatStandards.md | 10 +- docs/DevelopmentTips.md | 17 --- docs/MaintainerVersioning.md | 144 +++--------------- docs/PackagesAndPluginGuidelines.md | 12 +- docs/Plugin Architecture/Plugin Management.md | 20 --- docs/ProfileGuidelines.md | 2 +- docs/SDKGuidelines.md | 3 + docs/TESTING.md | 10 +- 9 files changed, 63 insertions(+), 183 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9b867c06a..1a62546ea 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -4,6 +4,7 @@ This document is a living summary of conventions and best practices for developm - [SIGN ALL OF YOUR GIT COMMITS](#sign-all-of-your-git-commits) - [Understanding Packages and Plug-ins](#understanding-packages-and-plug-ins) - [Pull Requests](#pull-requests) + - [Dependencies](#dependencies) - [Contributing to Core Functionality](#contributing-to-core-functionality) - [General Guidelines](#general-guidelines) - [Changelog Update Guidelines](#changelog-update-guidelines) @@ -61,7 +62,7 @@ For more information and guidelines for setting up your project, see [Packages a Determine if the infrastructure enhancement applies to Zowe CLI or Imperative CLI Framework, or if it is best suited as a plug-in to the core. -Zowe CLI is built on [Imperative CLI Framework](https://github.com/zowe/imperative/wiki). Most Zowe CLI core functionality is contained within the framework. Work in, or submit issues to, the Imperative CLI Framework repository when you want to enhance the following core functionalities: +Zowe CLI is built on [Imperative CLI Framework](https://github.com/zowe/zowe-cli/wiki). Most Zowe CLI core functionality is contained within the framework, such as: - REST client - Logging @@ -75,9 +76,18 @@ Zowe CLI is built on [Imperative CLI Framework](https://github.com/zowe/imperati Consider the following when you interact with pull requests: - Pull request reviewers should be assigned to a same-team member. -- Pull requests should remain open for at least 24 hours, or until close of business next business day (accounting for weekends and holidays). +- Pull requests should have at least 2 reviews before merging. - Anyone can comment on a pull request to request delay on merging or to get questions answered. +## Dependencies + +The CLI and Zowe Plug-ins use strict version numbers for dependencies. +Any SDKs should not pin dependencies unless it is absolutely required in order to function. + - ^ should be used to specify any dependency with the same major version. + - ~ should be used to specify any dependency with the same minor version. + +For Zowe organization repositories, all dependencies must be compatible with the EPL-2.0 license. + ## General Guidelines The following list describes general conventions for contributing to Zowe CLI: @@ -89,14 +99,18 @@ The following list describes general conventions for contributing to Zowe CLI: - Throw ImperativeError (or perhaps a wrapping of these) instead of throwing Error objects for automatic logging and node-report captures. - Provide adequate logging to diagnose problems that happen at external customer sites. - Avoid using/referencing to `zowe` or `Zowe CLI` within help, source file names, and errors - this name is subject to change. For example use `cli` instead. -- Keep "packages" small and independent without cross dependencies (e.g. `zosjobs` logically should not depend on `zosfiles` package) +- Keep "packages" small and independent, without cross dependencies whenever possible (e.g. `zosjobs` logically should not depend on `zosfiles` package, but may rely on `core` for core z/OSMF functionality) - When a package is dependent on another package, import the through the dependent package's interface (`index.ts`) e.g. `packages/zosjobs/src/GetJobs.ts` will import the `rest` package via: ```typescript - import { ZosmfRestClient } from "../../../rest"; + import { ZosmfRestClient } from "@zowe/core-for-zowe-sdk"; ``` NOT via: ```typescript + import { ZosmfRestClient } from "../../../rest"; + ``` + OR via: + ```typescript import { ZosmfRestClient } from "../../../rest/src/ZosmfRestClient"; ``` - Make classes small, logical pieces (e.g. instead of 1 `Jobs` class to hold all Job's APIs, we have `GetJobs`, `SubmitJobs`, `DeleteJobs`, etc...) @@ -195,9 +209,9 @@ Open an issue in the [docs-site repository](https://github.com/zowe/docs-site) i - End-user documentation on the Zowe Doc Site so that users can learn about your plug-in. Use existing plug-in topics as a model. - - A readme.md file within the plug-in repository that contains information for developers (overview, how to build from source, and how to run tests, at minimum). For example, see [the CICS plug-in readme](https://github.com/zowe/zowe-cli-cics-plugin#zowe-cli-plug-in-for-ibm-cics). + - A readme.md file within the plug-in repository that contains information for developers (overview, how to build from source, and how to run tests, at minimum). For example, see [the CICS plug-in readme](https://github.com/zowe/cics-for-zowe-client/tree/main/packages/cli#IBM-CICS-Plug-in-for-Zowe-CLI). - - a CONTRIBUTING.md file within the plug-in repository that lists specific considerations for contributing code to your plug-in (if any), and also links to the core CLI contribution guidelines. For an example, see [the CICS plug-in contribution guidelines](https://github.com/zowe/zowe-cli-cics-plugin/blob/master/CONTRIBUTING.md). + - a CONTRIBUTING.md file within the plug-in repository that lists specific considerations for contributing code to your plug-in (if any), and also links to the core CLI contribution guidelines. For an example, see [the CICS plug-in contribution guidelines](https://github.com/zowe/cics-for-zowe-client/blob/main/CONTRIBUTING.md). - When contributing **code/functionality to the core CLI**, we recommend that you provide the following: @@ -207,7 +221,7 @@ In addition to external documentation, please thoroughly comment your code for f ### JS Documentation -- Use jsdoc annotations - [document this](https://marketplace.visualstudio.com/items?itemName=joelday.docthis) makes extensive use of jsdoc tags. +- Use jsdoc annotations - Common tags to use, `@static`, `@memberof`, `@returns`, `@params`, `@class`, `@exports`, `@interface`, `@types`, `@throws`, `@link` - CLI auto-generated documentation is created via command definitions - [tsdoc](https://typedoc.org/) is used to generate html documentation diff --git a/docs/CommandFormatStandards.md b/docs/CommandFormatStandards.md index 81308b2d5..75608e37d 100644 --- a/docs/CommandFormatStandards.md +++ b/docs/CommandFormatStandards.md @@ -59,7 +59,7 @@ Refer to the following guidelines when writing descriptions for syntax segments - The `summary` is a one line, short description. This appears in the list of sub-segments on online help pages (for example, Zowe root help lists the groups with their short descriptions. Zowe group help lists the actions with their descriptions. - - Do NOT include punctuation at the end of a summary description for consistency. + - Do NOT include punctuation at the end of a summary for consistency. - The full `description` explains the purpose, intent, & usage of the group, action, object, or option. Ideally, include use cases that apply so that people understand the practical value. There is some tension between clarity and length. Extremely long descriptions can clutter the interface, but users want to know what they can accomplish with a given command. Some end users have indicated that they struggle to understand what the CLI is capable of and how they might use it, so good descriptions are essential. @@ -81,9 +81,9 @@ Research and usability testing has revealed that examples are the single most im - Positional arguments are a special kind of option. They are values/arguments entered that have an implicit option name and are usually entered immediately after the `object` (for example, the file name in the `zowe zos-files list dataset` command). These are usually required arguments. A single positional argument is most common but some commands have multiple positional arguments that are entered space-separated. We do not advise having multitple positional arguments because then the user must type several values in a row in the correct order, which can be error prone and hard to understand the proper syntax. Where there appears to be a need for multiple positional arguments, consider adding formal `option` names and make them required. -- Required options are listed under a Required Options section in the help. User research and usability testing have shown that statements explaining which options are required is among the most useful information in the online help pages, so it is important to write good descriptions and include these in the examples. +- Required options are listed under a `Required Options` section in the help. User research and usability testing have shown that statements explaining which options are required is among the most useful information in the online help pages, so it is important to write good descriptions and include these in the examples. -- Non-required options are listed under an Options section in the help. +- Non-required options are listed under an `Options` section in the help. - The help may include other categories of options for connecting to a service such as z/OSMF (for example, `--password`), setting profiles, and global options (for example,`response-format-json`) @@ -93,11 +93,11 @@ Research and usability testing has revealed that examples are the single most im - Dependencies between options can exist (if you specify one, you must specify the other, for example). This can introduce usability problems. The dependencies with other options should be noted in the option description. -- The arguments/values for an `option` can sometimes take wildcards (for example, a data-set name). The wildcard symbol is generally the asterisk * character. When building commands, consider using asterisk as the standard. +- The arguments/values for an `option` can sometimes take wildcards (for example, a data-set name). The wildcard symbol is generally the asterisk (*) character. When building commands, consider using asterisk as the standard. - The arguments/values can sometimes include quotes and can be a safer way to type the command. When writing examples, it is advisable to show arguments in quotes. -- Some options take array values. The standard format is space separated. For more information, see [ICommandPositionalDefinition.ts](https://github.com/zowe/imperative/blob/master/packages/cmd/src/doc/option/ICommandPositionalDefinition.ts). +- Some options take array values. The standard format is space separated. For more information, see [ICommandPositionalDefinition.ts](https://github.com/zowe/zowe-cli/blob/master/packages/imperative/src/cmd/src/doc/option/ICommandPositionalDefinition.ts). ## Abbreviated Command Structure diff --git a/docs/DevelopmentTips.md b/docs/DevelopmentTips.md index 08d6b9de8..78e1bb928 100644 --- a/docs/DevelopmentTips.md +++ b/docs/DevelopmentTips.md @@ -2,27 +2,10 @@ ## Contents - - [Linking Imperative from source](#linking-imperative-from-source) - [Debugging in VS Code](#debugging-in-vs-code) - [Profiling with `pprof`](#profiling-with-pprof) - [Using Development Mode](#using-development-mode) -## Linking Imperative from source - -If you make changes in a local copy of Imperative and want to test them in Zowe CLI, you need to replace the `node_modules/@zowe/imperative` directory with a symlink to the Imperative repo. - -To set up this symlink, run the following command at the top level of the Zowe CLI repo: - - npm run link:imperative - -The first time this command is run, you may see a warning that "Symlink wanted name was occupied by directory or file" which is safe to ignore. - -This command must be repeated to recreate the link after running `npm install` or any other command that updates dependencies in the `node_modules` folder. - -**Note:** The command assumes your Imperative repo is located in an `imperative` folder alongside your `zowe-cli` folder. If it is located somewhere else, run the command like this: - - npm run link:imperative -- - ## Debugging in VS Code Create a launch configuration like the following. You can have as many launch configurations as you want, each with their own name and set of arguments. diff --git a/docs/MaintainerVersioning.md b/docs/MaintainerVersioning.md index 23c127f11..7e13109d4 100644 --- a/docs/MaintainerVersioning.md +++ b/docs/MaintainerVersioning.md @@ -52,15 +52,21 @@ We tag various releases of our product in an NPM registry. End users install the This tag points to the "Active Development" version of the CLI. Breaking changes can be introduced to this version at any time. -* **`zowe-v1-lts`** +* **`zowe-v2-lts`** This tag points to the current Long Term Support (LTS) version of the product. **Note:** This version (what the tag points to) will be updated to introduce backward-compatible enhancements and bug fixes, but *not* breaking changes. -* **`lts-incremental`** +* **`zowe-v1-lts`** + + This tag points to the stable Long Term Support (LTS) version of the product. + + **Note:** This version (what the tag points to) will be updated to introduce backward-compatible bug fixes, but *not* enhancements or breaking changes. + +* **`lts-incremental` *DEPRECATED*** - This tag points to a a previous Long Term Support (LTS) version of the product. + This tag points to a previous Long Term Support (LTS) version of the product. **Note:** This version (what the tag points to) will only be updated to provide bug fixes. @@ -79,148 +85,38 @@ See the [example timeline](#example-timeline) for examples that show how the abo Our versioning scheme has the following requirements: * New features are not introduced for bug fixes. -* Support two stable releases: `@zowe-v1-lts` and `@lts-incremental` +* Support two stable releases: `@zowe-v2-lts` and `@zowe-v1-lts` * Each release must be supported for a minimum of one calendar year. ## Tentative Release Schedule -The following table shows a tentative Zowe CLI release schedule: - -| Zowe CLI Version | Validation Begin | Validation End | Begin Support | End Support | -| ------------- | ----------- | ----------- | ----------- | ----------- | -| 1.0.x | n/a | n/a | 05-30-2018 | *05-31-2019 | -| 2.x.x | n/a | 01-21-2019 | 01-22-2019 | 01-22-2020 | -| ``.x.x | *01-22-2019 | *01-21-2020 | *01-22-2020 | *01-22-2020 | - -**Notes:** -* The Date format is `MM-DD-YYYY`. -* This release schedule is subject to change. -* **`*`** This is a rough calculation. -* **``** The BreakingChange number validated when support begins. +See the [Zowe Community Release Schedule](https://github.com/zowe/community/blob/master/Project%20Management/Schedule/Zowe%20PI%20%26%20Sprint%20Cadence.md#Releases) ## Tag Usage The following is a list of commands that users issue to install product versions: -* To obtain the most current community edition version: +* To obtain the most current version: `npm install -g @zowe/cli` OR `npm install -g @zowe/cli@latest` * To obtain the supported incremental version: - `npm install -g @zowe/cli@zowe-v1-lts` + `npm install -g @zowe/cli@zowe-v2-lts` * To obtain the supported stable version: - `npm install -g @brightside/core@lts-incremental` - - -## Example timeline - -The version numbering below is not an exact sequence; it just represents possible sequences to help illustrate how this versioning process works. - -In this scenario, the following versions were released before this versioning scheme was implemented. The newest patches would have previously been labeled LTS-stable. - -``` -- 1.0.0 - - 1.0.1 - - 1.0.2 - - ... - - 1.0.10 @lts-stable -``` - -A breaking change is a trigger for a new LTS release. Thereafter, the newest non-breaking enhancement or bug fix would have been tagged with LTS-incremental. - -``` -- 2.0.0 - - 2.0.1 -- 2.1.0 - - 2.1.1 - - 2.1.2 - - 2.1.3 -- 2.2.0 - - 2.2.1 - - 2.2.2 - - 2.2.3 - - 2.2.4 @lts-incremental -``` - -Product Management (and the passing of another calendar year) determined that 1.0 should be decommissioned. Version 2.3.0 became LTS-incremental. Version 2.2.2 could have been tagged as LTS-stable. Thereafter, the LTS-stable tag would have moved forward with the newest 2.2.x patch above, and the LTS-incremental tag would have moved forward with the newest 2.x.x version below. - -``` -- 2.2.0 - - 2.2.1 - - 2.2.2 - - 2.2.3 - - 2.2.4 @lts-stable -- 2.3.0 - - 2.3.1 - - 2.3.2 -- 2.4.0 -- 2.5.0 @lts-incremental -``` - -Assume that the following example is our current point in time. Assume that 2.x has been decommissioned, and the 3.2.0 release is tagged as LTS-stable. Only patches (3.2.x) will be delivered for this LTS release. The LTS-stable tag will move to each such new patch release. - -``` -- 3.0.0 - - 3.0.1 - - 3.0.2 -- 3.1.0 - - 3.1.1 - - 3.1.2 -- 3.2.0 @LTS-stable -``` - -When 4.0.0 was delivered, it was tagged as LTS-incremental. Thereafter, each new non-breaking enhancement or bug fix was tagged as LTS-incremental. At this point in time, the 4.1.3 version is tagged as LTS-incremental. Additional non-breaking enhancements and bug fixes may be introduced in the future, and LTS-incremental will move to that new version. - -``` -- 4.0.0 - - 4.0.1 -- 4.1.0 - - 4.1.1 - - 4.1.2 - - 4.1.3 @lts-incremental -``` - -As we move forward in this scenario, development is also in progress on a 5.x feature-set which includes breaking changes. With each merge to our master branch, a new alpha version with a pre-release string is published. For example `5.4.0-alpha.201912301259`. It will be tagged as `@daily` to prevent NPM from automatically moving the latest tag to this new version. - -To provide an opportunity for validation of that new beta release, we wait for one sprint. At the end of each sprint, we republish the previous beta release with no pre-release string (5.6.0 in the example below) and label that release as `@latest`. We then move the `@beta` label to the newest pre-release produced in the recently completed sprint. - -``` -- 5.0.0 - - Numerous pre-releases -- 5.1.0 - - Numerous pre-releases - - 5.1.1 -- 5.2.0 - - Numerous pre-releases -- 5.3.0 - - Numerous pre-releases -- 5.4.0 - - Numerous pre-releases -- 5.5.0 @latest - Was assigned at the end of sprint N. -- 5.6.0-FirstDateInSprintN -- 5.6.0-SecondDateInSprintN -- 5.6.0-DateAtEndOfSprintN @beta - Was assigned at end of sprint N. -- 5.7.0-FirstDateInSprintN+1 -- 5.7.0-SecondDateInSprintN+1 -- 5.7.0-DateAtEndOfSprintN+1 Now move @beta to 5.7.0-DateAtEndOfSprintN+1 -- 5.6.0 Version 5.6.0 is published at the end of sprint N+1 - Now move @latest to 5.6.0 -``` + `npm install -g @zowe/cli@zowe-v1-lts` ## Specifying Compatible Versions in package.json Files -NPM packages typically depend on multiple other NPM packages. For example, Zowe CLI depends on our Imperative CLI Framework (@brightside/imperative). Similarly, Zowe CLI plug-ins depend on both Zowe CLI and Imperative CLI Framework (@brightside/core and @brightside/imperative). +NPM packages typically depend on multiple other NPM packages. For example, Zowe CLI depends on our Imperative CLI Framework (@zowe/imperative). Similarly, Zowe CLI plug-ins can depend on both Zowe CLI and Imperative CLI Frameworks (@zowe/core-for-zowe-sdk and @zowe/imperative). For each NPM package on which Zowe depends, an application specifies the version number with which it is compatible. The version specifier can be one specific version number (for example, `1.2.3`), but it does not have to be specific. If the version is too specific, application developers can be burdened with frequent updates to their package.json file to stay up-to-date with every patch produced by the dependent package. If the version is too broad, applications might be paired with a version of the dependent package that has new changes, which can break the application. ## Versions for Zowe CLI Dependencies within Plug-ins -In the peerDependencies property of a plug-in's package.json file, the plug-in specifies the versions of Zowe CLI and Imperative CLI Framework with which it is compatible. - -**Note:** `peerDependencies` will not be a requirement after **[issue 99](https://github.com/zowe/imperative/issues/99)** is resolved. +In the peerDependencies property of a plug-in's package.json file, the plug-in specifies the versions of the Imperative CLI Framework with which it is compatible. When you install a plug-in into Zowe CLI, the plug-in always uses the version of Zowe CLI APIs that are part of the installed application. It also uses the version of Imperative APIs that were installed as part of the Zowe CLI application. Plug-ins never get a different version of Zowe CLI or Imperative, regardless of the versions specified by the plug-in. However, the Zowe CLI plug-in installation program compares the versions specified by the plug-in with the actual versions of Zowe CLI and Imperative. It will issue warnings when incompatible versions were specified. This notifies the end user and the plug-in developer that corrective action is required to ensure that the plug-in works reliably with Zowe CLI. @@ -230,7 +126,7 @@ We recommend the following scheme for specifying Zowe CLI dependencies within pl ## Recommendation for Supported Versions of Plug-ins -In a supported release, a plug-in should specify that it wants versions of Zowe CLI and Imperative that remain backward-compatible with the versions that were in use when the plug-in reached its supported state. This can be expressed using the following format for both Zowe CLI and Imperative: +In a supported release, a plug-in should specify that it wants versions of Imperative that remain backward-compatible with the versions that were in use when the plug-in reached its supported state. This can be expressed using the following format for Imperative: ``` BreakingChangeUpdate.x OR BreakingChangeUpdate.Enhancement.x @@ -242,7 +138,7 @@ BreakingChangeUpdate.x OR BreakingChangeUpdate.Enhancement.x 2.x OR 2.2.x ``` -At the time that this document was published, Zowe CLI was at version `1.0.7` and Imperative was at `1.0.8`. Both packages' peerDependencies versions in a supported plug-in can be specified as `1.x`. This indicates that we anticipate that the plug-in will work with all upcoming bug fixes and with all new features that do not break backward-compatibility, such as `1.1.0`, or `1.4.6`, but not with `2.0.0` or greater). By specifying a version of `1.x`, the plug-in does not have to update its version string and republish frequently just to avoid compatibility warnings when patches and backward-compatible enhancements of Zowe CLI or Imperative are published. For a supported plug-in, this ties the plug-in to a reasonable range of non-breaking changes in Zowe CLI and Imperative. By the time that the next feature release of the plug-in be published, either Zowe CLI or Imperative might be specified as `2.x` and you would lock in that level of releases for the life of that supported version of the plug-in. +At the time that this document was published, Imperative was at version `1.0.8`. Imperative's peerDependencies version in a supported plug-in can be specified as `1.x`. This indicates that we anticipate that the plug-in will work with all upcoming bug fixes and with all new features that do not break backward-compatibility, such as `1.1.0`, or `1.4.6`, but not with `2.0.0` or greater). By specifying a version of `1.x`, the plug-in does not have to update its version string and republish frequently just to avoid compatibility warnings when patches and backward-compatible enhancements of Imperative are published. For a supported plug-in, this ties the plug-in to a reasonable range of non-breaking changes in Zowe CLI and Imperative. By the time that the next feature release of the plug-in be published, Imperative might be specified as `2.x` and you would lock in that level of releases for the life of that supported version of the plug-in. ## Recommendation for Pre-release Versions of plug-ins @@ -269,7 +165,7 @@ You can specify pre-release versions for plug-ins using one of the following met **Example:** ``` - @brightside/imperative": "1.1.0-next.201808241438" + @zowe/imperative": "1.1.0-next.201808241438" ``` Such a version matches only this one snapshot of the Zowe CLI or Imperative pre-release. The plug-in will have to change the version string with each new pre-release snapshot. This requires frequent updates to the plug-in's package.json file, but helps to ensure that the plug-in will never be accidentally compatible with a later stable version of that dependency. @@ -279,7 +175,7 @@ You can specify pre-release versions for plug-ins using one of the following met **Example:** ``` - @brightside/imperative": ">=1.1.0-0 + @zowe/imperative": ">=1.1.0-0 ``` Such a version matches every pre-release snapshot of `1.1.0`. However, it also matches every new feature release of the dependency (for example, `1.2.0`, `2.5.3`, `14.3.8`, and so on). A plug-in developer never has to change that version string during the pre-release development stage of the plug-in. However, the plug-in developer must remember to change the dependency version to a string such as `1.x` before publishing the supported release of the plug-in to avoid unintended compatibility with future versions of the dependent package. diff --git a/docs/PackagesAndPluginGuidelines.md b/docs/PackagesAndPluginGuidelines.md index e2871b88a..8eb999313 100644 --- a/docs/PackagesAndPluginGuidelines.md +++ b/docs/PackagesAndPluginGuidelines.md @@ -11,7 +11,8 @@ Plug-ins should use the [Zowe CLI Plug-in Starter Project](https://github.com/zo ## Plug-in Repositories -Name plug-in repositories according to the Zowe CLI `[group]` name. For example, the `cics` plug-in repository name is `/zowe-cli-cics-plugin`. +Name plug-in repositories according to the Zowe CLI `[group]` name. For example, the `cics` plug-in repository name is `zowe-cli-cics-plugin`. +Plug-in repositories may also have a different name for monorepos, such as `cics-for-zowe-clients`. **Note:** See [Command Format Standards](CommandFormatStandards.md) for details about `[group]`. @@ -26,6 +27,8 @@ The following directories and files are required in packages and plug-ins: - A `README.md` for instructions about building, testing, etc... For more information, see [Documentation Guidelines](../CONTRIBUTING.md#documentation-guidelines). - An `index.ts` for exports from your package or plug-in. +These directories may be under a subpath, such as `packages/cli`. + ### Package Directories In addition to the requirements described in [Directories](#directories), **packages** require the following directories and files: @@ -62,10 +65,11 @@ packages | └── __system__ | ├── api | └── cli - └── index.ts + ├── index.ts └── README.md ``` + ### Example Plug-in Structure The following diagram illustrates the plug-in directory structure @@ -109,7 +113,7 @@ cli └── Group.definition.ts ``` -## Profiles +## Profiles & Team Configuration Define profile types on the base imperative configuration document (found in the root `imperative/` directory). Packages and plug-ins can define their own profile type, or, they can take advantage of a previously defined profile type. For example, the `zos-files` and `zos-console` share a `zosmf` profile because both profile types use z/OSMF APIs. -For more information, see [Profile Guidelines](ProfileGuidelines.md). +For more information, see [Profile Guidelines](ProfileGuidelines.md) and [Using Team Configuration](./Using%20Team%20Configuration.md). diff --git a/docs/Plugin Architecture/Plugin Management.md b/docs/Plugin Architecture/Plugin Management.md index a1ec74267..48b2214a2 100644 --- a/docs/Plugin Architecture/Plugin Management.md +++ b/docs/Plugin Architecture/Plugin Management.md @@ -155,12 +155,6 @@ cli plugin list No arguments are sent to this command as it is meant to list all installed plugins and their status. That is good enough for now and could be built upon later. -#### Health Command - -The health command will list the health of all plugins or the plugins specified when sent to the command. This is useful as a first step in troubleshooting a plugin or base CLI as things such as missing methods and classes. Plugins also will need to implement a health check method that provides further diagnostic information about the plugin. - -This type of command is needed because it is feasible that a user could be using a plugin for some amount of time with no problem and then some kind of hiccup happens on their machine which breaks the plugin. The health check would be able to help the user quickly find the problem in their environment / plugin to get a quicker resolution to their problem. The information returned by this command could also be used in a bug report to the base CLI or plugin developer. - ##### Command Usage ```commandline cli plugin health [plugin...] @@ -181,20 +175,6 @@ cli plugin version - `` is the name of an installed plugin. If this plugin isn't installed, the command will report an error. -#### Repair Command - -This command will attempt to repair a plugin. - -It could be feasible that their might be some scenarios where a plugin might become corrupt or broken over time due to unforseen circumstances. Thus it would be ideal if there was a command that existed to easily fix a plugin. - -***NOTE:** This is not expected to be part of the first iteration.* - -Plugins would have to implement a corresponding `fix` method if they have the ability to repair themselves. One example of how this could be useful: - -Assume that a plugin didn't properly install a node_module or somehow one became missing. The plugin could implement a fix method, which could call it's health check to determine what the problem is. After determining that a required module isn't installed, the plugin could attempt to install all missing modules. - -This could also have been done by uninstalling and reinstalling the plugin but that could be considered a painfull process depending on the plugin. The repair command would make this process a bit easier. - ##### Command Usage ```commandline cli plugin repair diff --git a/docs/ProfileGuidelines.md b/docs/ProfileGuidelines.md index 6776fbb5a..0d1806335 100644 --- a/docs/ProfileGuidelines.md +++ b/docs/ProfileGuidelines.md @@ -8,7 +8,7 @@ The basic use case for a profile is to persist "connection details" (i.e. host/p Profiles are ultimately for user convenience. Having to repetitively type (or retype) sets of configuration/options can be cumbersome for a user. -See [Imperative CLI Framework documentation](https://github.com/zowe/imperative/wiki) about profiles for details on implementing profiles and the profile "type" concept. +See [Imperative CLI Framework documentation](https://github.com/zowe/zowe-cli/wiki) about profiles for details on implementing profiles and the profile "type" concept. ### When You Use a Profile to Store Configuration Items Use a profile to store configuration items under the following conditions: diff --git a/docs/SDKGuidelines.md b/docs/SDKGuidelines.md index 8576aaa28..0f86f32f7 100644 --- a/docs/SDKGuidelines.md +++ b/docs/SDKGuidelines.md @@ -34,6 +34,7 @@ The Zowe CLI monorepo contains: * `@zowe/zos-console-for-zowe-sdk` * `@zowe/zos-files-for-zowe-sdk` * `@zowe/zos-jobs-for-zowe-sdk` + * `@zowe/zos-logs-for-zowe-sdk` * `@zowe/zosmf-for-zowe-sdk` * `@zowe/zos-tso-for-zowe-sdk` * `@zowe/zos-uss-for-zowe-sdk` @@ -48,6 +49,8 @@ A CLI plugin monorepo should contain only two packages: * One CLI package (e.g., `@zowe/cics-for-zowe-cli`) * One SDK package (e.g., `@zowe/cics-for-zowe-sdk`) +A CLI plugin monorepo may also contain a VSCode Extension. + ## Package Versioning The following guidelines apply to versioning of SDKs for Zowe CLI and Zowe CLI plugins: diff --git a/docs/TESTING.md b/docs/TESTING.md index 04df1c0a0..71102ddcd 100644 --- a/docs/TESTING.md +++ b/docs/TESTING.md @@ -46,7 +46,7 @@ Package/Plugin integration tests are divided into two categories: - **CLI**: Issuing commands via script/exec and ensuring correctness of output (as a user at their terminal/console would). ### Integration Test Layout -- Place integration tests under the packages `__tests__/__integration__` directory. +- Place integration tests under the package's `__tests__/__integration__` directory. - Place **API** integration tests under `__tests__/__integration__/api` - Place **CLI** integration tests under `__tests__/__integration__/cli` - Arrange **API** & **CLI** integration test directories to match the structure of your **API** & **CLI** src directories. @@ -89,9 +89,9 @@ beforeAll(async () => { ``` -Temporary profiles are created using a randomized profile name to avoid collision with any existing profiles you may be using. The Zowe CLI home environmental variable is automatically set to the temporary directory created in the TestEnvironment.setUp function. If you do request any temporary profiles being created, please be sure to call TestEnvironment.cleanUp in an afterAll block as shown in the example above. +Temporary profiles are created using a randomized profile name to avoid collision with any existing profiles you may be using. The Zowe CLI home environmental variable is automatically set to the temporary directory created in the `TestEnvironment.setUp` function. If you do request any temporary profiles being created, please be sure to call `TestEnvironment.cleanUp` in an `afterAll` block as shown in the example above. -If you run the tests and forgot to call TestEnvironment.cleanUp, killed the process before the afterAll jest hook could run, +If you run the tests and forgot to call `TestEnvironment.cleanUp`, killed the process before the `afterAll` jest hook could run, or otherwise prevented the profiles from being deleted, you can clean up these stranded profiles by running the command `npm run test:cleanUpProfiles`. However, this script is dependent on the contents of the `__tests__/__results__/data`. If you have deleted that directory, you will have to clean up the credentials manually. @@ -124,5 +124,5 @@ See `__tests__/__scripts__/clean_profiles.sh` for more information Inter-package integration tests should consist of "real-world" scenarios that involve multiple commands or APIs. For example, Creating a source data set, uploading an ASMPGM, compiling the ASMPGM, and running the ASMPGM. [jest]: https://facebook.github.io/jest/ -[Integration Tests]: ./packages/PackagesAndPluginGuidelines.md#integration-tests -[PackagesAndPluginGuidelines.md]: ./packages/PackagesAndPluginGuidelines.md +[Integration Tests]: ./PackagesAndPluginGuidelines.md#integration-tests +[PackagesAndPluginGuidelines.md]: ./PackagesAndPluginGuidelines.md From 3c84c3c3fbd4691c2659ea77a838748d61ab75d1 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Thu, 29 Aug 2024 14:41:15 -0400 Subject: [PATCH 05/14] Make requested changes Signed-off-by: Andrew W. Harn --- CONTRIBUTING.md | 2 +- docs/MaintainerVersioning.md | 2 +- docs/PackagesAndPluginGuidelines.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1a62546ea..f0b11255c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -76,7 +76,7 @@ Zowe CLI is built on [Imperative CLI Framework](https://github.com/zowe/zowe-cli Consider the following when you interact with pull requests: - Pull request reviewers should be assigned to a same-team member. -- Pull requests should have at least 2 reviews before merging. +- Pull requests should have at least 2 approving reviews before merging. - Anyone can comment on a pull request to request delay on merging or to get questions answered. ## Dependencies diff --git a/docs/MaintainerVersioning.md b/docs/MaintainerVersioning.md index 7e13109d4..f6efa589f 100644 --- a/docs/MaintainerVersioning.md +++ b/docs/MaintainerVersioning.md @@ -100,7 +100,7 @@ The following is a list of commands that users issue to install product versions `npm install -g @zowe/cli` OR `npm install -g @zowe/cli@latest` -* To obtain the supported incremental version: +* To obtain the supported active LTS version: `npm install -g @zowe/cli@zowe-v2-lts` diff --git a/docs/PackagesAndPluginGuidelines.md b/docs/PackagesAndPluginGuidelines.md index 8eb999313..f69c620ea 100644 --- a/docs/PackagesAndPluginGuidelines.md +++ b/docs/PackagesAndPluginGuidelines.md @@ -11,8 +11,8 @@ Plug-ins should use the [Zowe CLI Plug-in Starter Project](https://github.com/zo ## Plug-in Repositories -Name plug-in repositories according to the Zowe CLI `[group]` name. For example, the `cics` plug-in repository name is `zowe-cli-cics-plugin`. -Plug-in repositories may also have a different name for monorepos, such as `cics-for-zowe-clients`. +Name plug-in repositories according to the Zowe CLI `[group]` name. For example, the `ftp` plug-in repository name is `zowe-cli-ftp-plugin`. +Plug-in repositories may also have a different name for monorepos, such as `cics-for-zowe-client`. **Note:** See [Command Format Standards](CommandFormatStandards.md) for details about `[group]`. From 69154ce5c607577863699c52770817d42e268956 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Tue, 3 Sep 2024 16:27:06 -0400 Subject: [PATCH 06/14] Remove incorrect commands Signed-off-by: Andrew W. Harn --- docs/MaintainerVersioning.md | 8 +- docs/Plugin Architecture/Plugin Management.md | 195 +----------------- 2 files changed, 11 insertions(+), 192 deletions(-) diff --git a/docs/MaintainerVersioning.md b/docs/MaintainerVersioning.md index f6efa589f..77627e379 100644 --- a/docs/MaintainerVersioning.md +++ b/docs/MaintainerVersioning.md @@ -165,19 +165,19 @@ You can specify pre-release versions for plug-ins using one of the following met **Example:** ``` - @zowe/imperative": "1.1.0-next.201808241438" + @zowe/imperative": "8.0.0-next-202408131445" ``` Such a version matches only this one snapshot of the Zowe CLI or Imperative pre-release. The plug-in will have to change the version string with each new pre-release snapshot. This requires frequent updates to the plug-in's package.json file, but helps to ensure that the plug-in will never be accidentally compatible with a later stable version of that dependency. -* The plug-in can specify that it wants any version of the peerDependency starting with the earliest version of the current pre-release and any later version going forward. +* The plug-in can specify that it wants any version of the peerDependency starting with the earliest version of the current pre-release and any later version going forward. This includes all GA versions of the peerDependency with the same major version, starting at 8.0.0: **Example:** ``` - @zowe/imperative": ">=1.1.0-0 + @zowe/imperative": ">=8.0.0-next-202408131445 <9.0.0" ``` - Such a version matches every pre-release snapshot of `1.1.0`. However, it also matches every new feature release of the dependency (for example, `1.2.0`, `2.5.3`, `14.3.8`, and so on). A plug-in developer never has to change that version string during the pre-release development stage of the plug-in. However, the plug-in developer must remember to change the dependency version to a string such as `1.x` before publishing the supported release of the plug-in to avoid unintended compatibility with future versions of the dependent package. + Such a version matches every pre-release snapshot of `8.0.0`. However, it also matches every new feature release of the dependency (for example, `8.1.0`, `8.1.1`, and so on). A plug-in developer never has to change that version string during the pre-release development stage of the plug-in. However, the plug-in developer must remember to change the dependency version to a string such as `^8.0.0` before publishing the supported release of the plug-in to avoid unintended compatibility with future versions of the dependent package, or declared compatibility with a pre-release. In either of these methods, plug-in developers must change their desired version more frequently and at critical milestones, which is an acceptable approach because the plug-in itself is in pre-release mode. The plug-in should stay in lockstep with Zowe CLI until the plug-in pre-release becomes a supported release. diff --git a/docs/Plugin Architecture/Plugin Management.md b/docs/Plugin Architecture/Plugin Management.md index 48b2214a2..a0197364e 100644 --- a/docs/Plugin Architecture/Plugin Management.md +++ b/docs/Plugin Architecture/Plugin Management.md @@ -49,7 +49,7 @@ When enabling plugins, a group will automatically be added to the Base CLI by th From the command line this would look something like this: ```commandline -cli plugin +zowe plugins ``` ### Commands @@ -93,14 +93,14 @@ To prevent duplication, this definition has been moved [here][plugin.json format ##### Command Usage ```commandline -cli plugin install [plugin...] [--registry ] [--isLocalURI] [--isRemoteURI] [--use ] +zowe plugins install [plugin...] [--registry ] [--isLocalURI] [--isRemoteURI] [--use ] ``` - `[plugin...]` is an npm package or a pointer to a URI (either local or remote). It is passed the same way it would be to npm install. - - Semantic versioning should also be handled for each plugin much like how it is done in `npm install`. So versions for plugins could be specified like `cli plugin install plugin@^1.0.0` and this would be saved in the plugin.json file so that the update command can respect this. + - Semantic versioning should also be handled for each plugin much like how it is done in `npm install`. So versions for plugins could be specified like `zowe plugins install plugin@^1.0.0` and this would be saved in the plugin.json file so that the update command can respect this. - In the instance that no version is specified, the latest version will be installed and prefixed with the same thing stored in npm's save-prefix. See [npm save prefix]. - For information on npm's semantic versioning, see [npm semver]. - Also like `npm install`, the ability to install multiple plugins in one command should be considered. - - `cli plugin install plugin1 plugin2 plugin3` (consistent with npm) + - `zowe plugins install plugin1 plugin2 plugin3` (consistent with npm) - ***NOTE:** Assume this format for the rest of the document when referring to `plugin...` type arguments.* - This parameter has been marked as optional so that it works like an npm install would in a project. In the first iteration, this functionality probably doesn't exist. In the event that no parameters are passed, a plugin.json file will need to exist or be provided. All plugins in this file will be installed using the same concept that `npm install` uses with a package.json. - ***NOTE:** This is not part of the first iteration.* @@ -117,7 +117,7 @@ This command is less complicated than the install command. Basically all this co ##### Command Usage ```commandline -cli plugin uninstall +zowe plugins uninstall ``` - `` is a list of installed plugins to uninstall. This would be the value of one of the keys in plugins.json. @@ -133,7 +133,7 @@ For instances where the update is done on an npm package at a given registry. Th ##### Command Usage ```commandline -cli plugin update [plugin...] [--registry ] +zowe plugins update [plugin...] [--registry ] ``` - **[plugin...]** is a list of installed plugins to update. This would be the value of one of the keys in plugins.json. It should be noted that this parameter could be optional. If omitted, all plugins would be updated to the most current version (which is determined in the plugin.json file). @@ -150,192 +150,11 @@ The list command will list all installed plugins to the Base CLI application. Th ##### Command Usage ```commandline -cli plugin list +zowe plugins list ``` No arguments are sent to this command as it is meant to list all installed plugins and their status. That is good enough for now and could be built upon later. -##### Command Usage -```commandline -cli plugin health [plugin...] -``` - -- `[plugin...]` is an optional list of plugins to perform a health check on. If no plugins are specified, then all plugins will be checked by this command. - -#### Version Command - -This command will print out the version of a plugin. - -This could be used by an automation script in a development environment to ensure that proper versions of a plugin are installed acrossed team members' machines. For example, say that a team is using `cli` with `cli-plugin` version 1 but version 2 is released and some of the build processes now need functionality in version 2. A script could be written to check these versions and perform updates as needed. - -##### Command Usage -```commandline -cli plugin version -``` - -- `` is the name of an installed plugin. If this plugin isn't installed, the command will report an error. - -##### Command Usage -```commandline -cli plugin repair -``` - -- `` is the name of an installed plugin. If the plugin is not broken, then nothing should happen. If the plugin is broken and the repair is successful, a simple success message will suffice. On a failed repair, a detailed message (and possible stack trace) should be printed to console.error. - -#### Help Command - -The help command would display additional plugin help. Some of these things could be: - -- Plain text to output in the console. -- A local HTML/PDF/TXT/MD file that opens in an appropriate application -- Some form of online help that is opened in the browser. - - GitHub - - Doc Site - -For this to be a good experience for plugin developers, some utility functions will need to be written to open up links or local files. Plugins will also need to implement a `help` function / variable that is called by the framework. - -##### Command Usage -```commandline -cli plugin help [arg] -``` - -- `` is the name of the plugin to display help for. -- `[arg]` is an optional argument to send to the help function of a plugin. This could be used to open up more contextual help. - -#### Add Command - -The add command would add preinstalled plugins to the plugins.json file so that the base CLI can make use of them. - -Imagine that a user went to their global install of a cli and started doing npm installs of plugins there, the add command could then be used to initialize the nessary config to use them. This could be extended at some point in the future to allow plugins to be installed via `npm install -g ` and then added with this command. - -##### Command Usage -```commandline -cli plugin add -``` - -- `` is a variable length list of plugins to be added to the base CLI. -- Plugins listed are expected to be in the node_modules directory already. Could be achieved by the user manually doing an `npm install` in the install directory. - - This could be expanded to also try to look in the global node_modules. - -#### Clean Command - -The clean command could be used to completely blow away a single plugin or all plugins in the case that the plugin environment becomes broken or poluted. Files, installiation, global set options should be allowed to be selectivly blown away or done in bulk. - -Execution of this command should also require the user to confirm that they wish to perform this action since it could be considered to be destructive. - -##### Command Usage -```commandline -cli plugin clean [plugin...] [--config] [--files] -``` - -- `[plugin...]` is an optional variable length argument that points to an installed plugin. - - If this parameter is omitted, then the operation affects all plugins. -- Operation flags - - Specifying no flags, will cause the clean operation to remove the package from node_modules and plugin.json. This also implies `--config` and `--files`. - - `--config` will cause the clean operation to remove any global configuration options that were set for the plugin. This does not remove the plugin and should be considered the first step in troubleshooting a plugin. - - `--files` will cause the clean operation to remove any files that were created by the plugin in the global CLI's storage location. - - This implies that we need to provide a way for plugins to create files in the CLI's storage folder (same location where profiles and config options are stored). - - This should also be a first step in troubleshooting a plugin or base CLI. - -***NOTE:** This doesn't need to be included in the first iteration as this isn't needed for an MVP plugin management facility. However, this is useful because it provides an easy way of cleaning up plugins besides the user of a CLI manually going in and deleting stuff. It also gives the ability to clean up config and files which could also be causing the problem, but would persist through a reinstall of a plugin.* - - -## Config Group - -As discussed in the plugin group, and agreed on by the team, global plugin configuration will be handled through the `cli config` command. This command should be provided with the Imperative framework and should be customizable (to a certain extent) by application built in the framework. - -So assuming that this `config` group exists, we will need to extend the existing functionality to allow plugin global configurations to be modified. This could be done in one of two ways. - -### Using --plugin - -Under this method, a flag would be used to specify the plugin name a configuration option should be set for. The usage would look something like this: - -- `cli config get --plugin ` -- `cli config set --plugin ` - -Some things to note: -- If `--plugin` is not specified, then the action is performed on the base CLI application. -- There needs to be a way that all configuration for the base CLI can be gotten as well as all configuration for plugins as well. This could be achieved by simply assuming that omitting the variable name on the get means return everything. - -#### Pros -- It is very easy to determine if you are configuring a plugin or the base CLI. -- It keeps the syntax of the config get/set commands fairly clean - -#### Cons -- This could lead to much longer commands for the user. -- It would be really difficult for two plugins to share the same global configuration options. - -### Prefixing Variables - -The other alternative is to prefix the variables with either the plugin name or a configurable prefix set by the plugin developers. The usage could look something like this: - -- `cli config get #` -- `cli config set # ` - -Now you may be wondering why the `#` symbol is being used, this is to help differentiate a plugin from a normal variable group that may exist. It could have been a `.` to be more familiar with JavaScript syntax (dot accessors), but that would have made this situation much harder to solve: - -Say that you have a global variable for your base CLI called `A.B` and you install a plugin that saves it's global configuration under the prefix `A`. Well then what would `cli config get A.B` do? Well in this scenario it could do one of two things: - -1. Gets the value of `A.B` in the base CLI -1. Gets the value of `B` from the plugin A - -There is no good way to discern between either of these methods. Under the `#` syntax, it is real easy for us to determine which configuration to get and set. Below are examples on how to do both of previously listed possibilities for `cli config get A.B`: - -1. `cli config get A.B` -1. `cli config get A#B` - -Now back to the prefixes. These could be defined by plugins and if not set it is defaulted to the plugin name. This gives some flexibility by plugin developers and could allow plugins to work together and build upon each other fairly easily. - -#### Pros -- Shorter command syntax -- Plugins could share prefixes - - Really good for plugins developed by the same vendor as there could be some overlapping options. -- Similar to JavaDoc and JSDoc in the sense of members of a class can be denoted by **className#memberName** - -#### Cons -- It could be a bit confusing to see something like this: `cli config get A#B.C.D` -- It could cause plugins to not be compatible if they are using the same prefix and variable names. - - **Example:** Plugin **A** uses prefix `A` and plugin **Alpha** uses prefix `A` but the two plugins have not been developed to work together. If these two plugins have the same global variable B of different types between the two, then unpredictable things will happen. - - The above problem can be prevented by having plugins specify a well defined configuration structure. If two plugins are using the same `prefix#variable` structure, then the types better match or a problem could be listed during the plugin health check. - -#### Dot Notation for Config - -So why bother talking about the dot notation for configuration? Well for starters it can already be seen in some CLIs, such as git's `user.name` and `user.email` but it also can relate to how configurations would be stored in JSON. - -Take the following two JSON files: - -###### /config/global.json -```JSON -{ - "A": { - "B": "VALUE", - "C": 1, - "D": false, - "E": [ - 1, - 2, - 3 - ] - } -} -``` - -###### /config/plugin/A.JSON -```JSON -{ - "B": 42 -} -``` - -Is it clearer how the dot notation plays into all of this? Below is the list of all the commands and output that can be seen from the get command: - -- `cli config get A.B` -> **VALUE** -- `cli config get A.C` -> **1** -- `cli config get A.D` -> **false** -- `cli config get A.E` -> **1, 2, 3** -- `cli config get A#B` -> **42** - - [Plugin Workflow]: ./High_Level_Plugin_Workflow.png [Config Group]: #config-group [npm semver]: https://docs.npmjs.com/misc/semver From 596b08c72894a6f6ca185aee56463c6779128ef2 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Wed, 4 Sep 2024 14:39:09 -0400 Subject: [PATCH 07/14] Fix missing quote Signed-off-by: Andrew W. Harn --- docs/MaintainerVersioning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/MaintainerVersioning.md b/docs/MaintainerVersioning.md index 77627e379..2d68290ae 100644 --- a/docs/MaintainerVersioning.md +++ b/docs/MaintainerVersioning.md @@ -165,7 +165,7 @@ You can specify pre-release versions for plug-ins using one of the following met **Example:** ``` - @zowe/imperative": "8.0.0-next-202408131445" + "@zowe/imperative": "8.0.0-next-202408131445" ``` Such a version matches only this one snapshot of the Zowe CLI or Imperative pre-release. The plug-in will have to change the version string with each new pre-release snapshot. This requires frequent updates to the plug-in's package.json file, but helps to ensure that the plug-in will never be accidentally compatible with a later stable version of that dependency. @@ -175,7 +175,7 @@ You can specify pre-release versions for plug-ins using one of the following met **Example:** ``` - @zowe/imperative": ">=8.0.0-next-202408131445 <9.0.0" + "@zowe/imperative": ">=8.0.0-next-202408131445 <9.0.0" ``` Such a version matches every pre-release snapshot of `8.0.0`. However, it also matches every new feature release of the dependency (for example, `8.1.0`, `8.1.1`, and so on). A plug-in developer never has to change that version string during the pre-release development stage of the plug-in. However, the plug-in developer must remember to change the dependency version to a string such as `^8.0.0` before publishing the supported release of the plug-in to avoid unintended compatibility with future versions of the dependent package, or declared compatibility with a pre-release. From a7951b816da3d329856cfafd8d4ecbe285a5893c Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Wed, 4 Sep 2024 16:10:05 -0400 Subject: [PATCH 08/14] Make requested changes Signed-off-by: Andrew W. Harn --- CONTRIBUTING.md | 12 ++++++------ docs/CommandFormatStandards.md | 4 ++-- docs/MaintainerVersioning.md | 6 +++--- docs/Plugin Architecture/Plugin Management.md | 2 +- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f0b11255c..b8a88c7a5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -81,10 +81,10 @@ Consider the following when you interact with pull requests: ## Dependencies -The CLI and Zowe Plug-ins use strict version numbers for dependencies. +The CLI and Zowe plug-ins use strict version numbers for dependencies. Any SDKs should not pin dependencies unless it is absolutely required in order to function. - - ^ should be used to specify any dependency with the same major version. - - ~ should be used to specify any dependency with the same minor version. + - `^` should be used to specify any dependency with the same major version. + - `~` should be used to specify any dependency with the same minor version. For Zowe organization repositories, all dependencies must be compatible with the EPL-2.0 license. @@ -207,11 +207,11 @@ Open an issue in the [docs-site repository](https://github.com/zowe/docs-site) i - When contributing **a plug-in**, we recommend that you provide the following: - - End-user documentation on the Zowe Doc Site so that users can learn about your plug-in. Use existing plug-in topics as a model. + - End-user documentation on the Zowe Docs site so that users can learn about your plug-in. Use existing plug-in topics as a model. - - A readme.md file within the plug-in repository that contains information for developers (overview, how to build from source, and how to run tests, at minimum). For example, see [the CICS plug-in readme](https://github.com/zowe/cics-for-zowe-client/tree/main/packages/cli#IBM-CICS-Plug-in-for-Zowe-CLI). + - A readme.md file within the plug-in repository that contains information for developers (overview, how to build from source, and how to run tests, at minimum). For an example, see [the CICS plug-in readme](https://github.com/zowe/cics-for-zowe-client/tree/main/packages/cli#IBM-CICS-Plug-in-for-Zowe-CLI). - - a CONTRIBUTING.md file within the plug-in repository that lists specific considerations for contributing code to your plug-in (if any), and also links to the core CLI contribution guidelines. For an example, see [the CICS plug-in contribution guidelines](https://github.com/zowe/cics-for-zowe-client/blob/main/CONTRIBUTING.md). + - A CONTRIBUTING.md file within the plug-in repository that lists specific considerations for contributing code to your plug-in (if any), and also links to the core CLI contribution guidelines. For an example, see [the CICS plug-in contribution guidelines](https://github.com/zowe/cics-for-zowe-client/blob/main/CONTRIBUTING.md). - When contributing **code/functionality to the core CLI**, we recommend that you provide the following: diff --git a/docs/CommandFormatStandards.md b/docs/CommandFormatStandards.md index 75608e37d..289370656 100644 --- a/docs/CommandFormatStandards.md +++ b/docs/CommandFormatStandards.md @@ -59,7 +59,7 @@ Refer to the following guidelines when writing descriptions for syntax segments - The `summary` is a one line, short description. This appears in the list of sub-segments on online help pages (for example, Zowe root help lists the groups with their short descriptions. Zowe group help lists the actions with their descriptions. - - Do NOT include punctuation at the end of a summary for consistency. + - For consistency, do NOT include punctuation at the end of a summary. - The full `description` explains the purpose, intent, & usage of the group, action, object, or option. Ideally, include use cases that apply so that people understand the practical value. There is some tension between clarity and length. Extremely long descriptions can clutter the interface, but users want to know what they can accomplish with a given command. Some end users have indicated that they struggle to understand what the CLI is capable of and how they might use it, so good descriptions are essential. @@ -93,7 +93,7 @@ Research and usability testing has revealed that examples are the single most im - Dependencies between options can exist (if you specify one, you must specify the other, for example). This can introduce usability problems. The dependencies with other options should be noted in the option description. -- The arguments/values for an `option` can sometimes take wildcards (for example, a data-set name). The wildcard symbol is generally the asterisk (*) character. When building commands, consider using asterisk as the standard. +- The arguments/values for an `option` can sometimes take wildcards (for example, a data set name). The wildcard symbol is generally the asterisk (*) character. When building commands, consider using asterisk as the standard. - The arguments/values can sometimes include quotes and can be a safer way to type the command. When writing examples, it is advisable to show arguments in quotes. diff --git a/docs/MaintainerVersioning.md b/docs/MaintainerVersioning.md index 2d68290ae..0133c83d5 100644 --- a/docs/MaintainerVersioning.md +++ b/docs/MaintainerVersioning.md @@ -116,7 +116,7 @@ For each NPM package on which Zowe depends, an application specifies the version ## Versions for Zowe CLI Dependencies within Plug-ins -In the peerDependencies property of a plug-in's package.json file, the plug-in specifies the versions of the Imperative CLI Framework with which it is compatible. +In the `peerDependencies` property of a plug-in's `package.json` file, the plug-in specifies the versions of the Imperative CLI Framework with which it is compatible. When you install a plug-in into Zowe CLI, the plug-in always uses the version of Zowe CLI APIs that are part of the installed application. It also uses the version of Imperative APIs that were installed as part of the Zowe CLI application. Plug-ins never get a different version of Zowe CLI or Imperative, regardless of the versions specified by the plug-in. However, the Zowe CLI plug-in installation program compares the versions specified by the plug-in with the actual versions of Zowe CLI and Imperative. It will issue warnings when incompatible versions were specified. This notifies the end user and the plug-in developer that corrective action is required to ensure that the plug-in works reliably with Zowe CLI. @@ -138,7 +138,7 @@ BreakingChangeUpdate.x OR BreakingChangeUpdate.Enhancement.x 2.x OR 2.2.x ``` -At the time that this document was published, Imperative was at version `1.0.8`. Imperative's peerDependencies version in a supported plug-in can be specified as `1.x`. This indicates that we anticipate that the plug-in will work with all upcoming bug fixes and with all new features that do not break backward-compatibility, such as `1.1.0`, or `1.4.6`, but not with `2.0.0` or greater). By specifying a version of `1.x`, the plug-in does not have to update its version string and republish frequently just to avoid compatibility warnings when patches and backward-compatible enhancements of Imperative are published. For a supported plug-in, this ties the plug-in to a reasonable range of non-breaking changes in Zowe CLI and Imperative. By the time that the next feature release of the plug-in be published, Imperative might be specified as `2.x` and you would lock in that level of releases for the life of that supported version of the plug-in. +At the time that this document was published, Imperative was at version `1.0.8`. Imperative's `peerDependencies` version in a supported plug-in can be specified as `1.x`. This indicates that we anticipate that the plug-in will work with all upcoming bug fixes and with all new features that do not break backward-compatibility, such as `1.1.0`, or `1.4.6`, but not with `2.0.0` or greater. By specifying a version of `1.x`, the plug-in does not have to update its version string and republish frequently just to avoid compatibility warnings when patches and backward-compatible enhancements of Imperative are published. For a supported plug-in, this ties the plug-in to a reasonable range of non-breaking changes in Zowe CLI and Imperative. By the time that the next feature release of the plug-in is published, Imperative might be specified as `2.x` and you would lock in that level of releases for the life of that supported version of the plug-in. ## Recommendation for Pre-release Versions of plug-ins @@ -170,7 +170,7 @@ You can specify pre-release versions for plug-ins using one of the following met Such a version matches only this one snapshot of the Zowe CLI or Imperative pre-release. The plug-in will have to change the version string with each new pre-release snapshot. This requires frequent updates to the plug-in's package.json file, but helps to ensure that the plug-in will never be accidentally compatible with a later stable version of that dependency. -* The plug-in can specify that it wants any version of the peerDependency starting with the earliest version of the current pre-release and any later version going forward. This includes all GA versions of the peerDependency with the same major version, starting at 8.0.0: +* The plug-in can specify that it wants any version of the `peerDependency` starting with the earliest version of the current pre-release and any later version going forward. This includes all GA versions of the `peerDependency` with the same major version, starting at 8.0.0: **Example:** diff --git a/docs/Plugin Architecture/Plugin Management.md b/docs/Plugin Architecture/Plugin Management.md index a0197364e..b3e6afe91 100644 --- a/docs/Plugin Architecture/Plugin Management.md +++ b/docs/Plugin Architecture/Plugin Management.md @@ -96,7 +96,7 @@ To prevent duplication, this definition has been moved [here][plugin.json format zowe plugins install [plugin...] [--registry ] [--isLocalURI] [--isRemoteURI] [--use ] ``` - `[plugin...]` is an npm package or a pointer to a URI (either local or remote). It is passed the same way it would be to npm install. - - Semantic versioning should also be handled for each plugin much like how it is done in `npm install`. So versions for plugins could be specified like `zowe plugins install plugin@^1.0.0` and this would be saved in the plugin.json file so that the update command can respect this. + - Semantic versioning should also be handled for each plugin much like how it is done in `npm install`. So versions for plugins could be specified like `zowe plugins install plugin@^1.0.0` and this would be saved in the `plugin.json` file so that the update command can respect this. - In the instance that no version is specified, the latest version will be installed and prefixed with the same thing stored in npm's save-prefix. See [npm save prefix]. - For information on npm's semantic versioning, see [npm semver]. - Also like `npm install`, the ability to install multiple plugins in one command should be considered. From e51a6d8baa856a59fd8e41ffc53658e536b96a7b Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Thu, 5 Sep 2024 14:21:47 -0400 Subject: [PATCH 09/14] Update workflow permissions Signed-off-by: Andrew W. Harn --- .github/workflows/auto-comment.yml | 2 ++ .github/workflows/rust-cli-publish.yml | 3 +++ .github/workflows/zowe-cli.yml | 3 +++ 3 files changed, 8 insertions(+) diff --git a/.github/workflows/auto-comment.yml b/.github/workflows/auto-comment.yml index 952eeffd9..c54034e5d 100644 --- a/.github/workflows/auto-comment.yml +++ b/.github/workflows/auto-comment.yml @@ -3,6 +3,8 @@ name: Zowe CLI Auto Responder for New Issues on: issues: types: labeled +permissions: + issues: write jobs: processLabelAction: diff --git a/.github/workflows/rust-cli-publish.yml b/.github/workflows/rust-cli-publish.yml index 33632fc77..5ac7699de 100644 --- a/.github/workflows/rust-cli-publish.yml +++ b/.github/workflows/rust-cli-publish.yml @@ -9,6 +9,9 @@ on: - 'zowex/**' - '.github/workflows/rust-cli*.yml' +permissions: + contents: write + jobs: release: diff --git a/.github/workflows/zowe-cli.yml b/.github/workflows/zowe-cli.yml index 6d9873e55..7406b901e 100644 --- a/.github/workflows/zowe-cli.yml +++ b/.github/workflows/zowe-cli.yml @@ -164,6 +164,9 @@ jobs: if: github.event_name == 'push' && github.ref_protected needs: test runs-on: ubuntu-latest + permissions: + issues: write + contents: write steps: - name: Checkout From 12e810dba46a35b87ead2fed2aa399dcfb44d1b5 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Thu, 5 Sep 2024 14:24:32 -0400 Subject: [PATCH 10/14] Add missing pull-requests permission Signed-off-by: Andrew W. Harn --- .github/workflows/zowe-cli.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/zowe-cli.yml b/.github/workflows/zowe-cli.yml index 7406b901e..19dc15657 100644 --- a/.github/workflows/zowe-cli.yml +++ b/.github/workflows/zowe-cli.yml @@ -167,6 +167,7 @@ jobs: permissions: issues: write contents: write + pull-requests: write steps: - name: Checkout From 20123b182fd1c3132862ef544c11d1c7cc920637 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Fri, 6 Sep 2024 09:19:22 -0400 Subject: [PATCH 11/14] Add write permission to PRs Signed-off-by: Andrew W. Harn --- .github/workflows/update-project.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/update-project.yml b/.github/workflows/update-project.yml index 669458776..d429d59f2 100644 --- a/.github/workflows/update-project.yml +++ b/.github/workflows/update-project.yml @@ -12,6 +12,9 @@ env: PR_STATUS_DRAFT: 'In Progress' PR_STATUS_READY: 'Review/QA' +permissions: + pull-requests: write + jobs: update-project: name: Move project item From 65f978bb9d6eee3c0348890a39d404917e2ae9fa Mon Sep 17 00:00:00 2001 From: zowe-robot Date: Mon, 9 Sep 2024 16:03:29 +0000 Subject: [PATCH 12/14] Bump version to 8.0.0-next.202409091603 [ci skip] Signed-off-by: zowe-robot --- .../__packages__/cli-test-utils/package.json | 4 +- lerna.json | 2 +- npm-shrinkwrap.json | 122 +++++++++--------- packages/cli/package.json | 28 ++-- packages/core/package.json | 6 +- packages/imperative/package.json | 4 +- packages/provisioning/package.json | 8 +- packages/secrets/package.json | 2 +- packages/workflows/package.json | 10 +- packages/zosconsole/package.json | 8 +- packages/zosfiles/package.json | 10 +- packages/zosjobs/package.json | 10 +- packages/zoslogs/package.json | 8 +- packages/zosmf/package.json | 8 +- packages/zostso/package.json | 10 +- packages/zosuss/package.json | 6 +- 16 files changed, 123 insertions(+), 123 deletions(-) diff --git a/__tests__/__packages__/cli-test-utils/package.json b/__tests__/__packages__/cli-test-utils/package.json index 0ee125abd..21dbd7e33 100644 --- a/__tests__/__packages__/cli-test-utils/package.json +++ b/__tests__/__packages__/cli-test-utils/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/cli-test-utils", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Test utilities package for Zowe CLI plug-ins", "author": "Zowe", "license": "EPL-2.0", @@ -43,7 +43,7 @@ "devDependencies": { "@types/js-yaml": "^4.0.9", "@types/uuid": "^10.0.0", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" diff --git a/lerna.json b/lerna.json index 0088d1bff..c927a051e 100644 --- a/lerna.json +++ b/lerna.json @@ -1,5 +1,5 @@ { - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "command": { "publish": { "ignoreChanges": [ diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json index e7fbe458c..fbe1f8c51 100644 --- a/npm-shrinkwrap.json +++ b/npm-shrinkwrap.json @@ -52,7 +52,7 @@ }, "__tests__/__packages__/cli-test-utils": { "name": "@zowe/cli-test-utils", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "find-up": "^5.0.0", @@ -63,7 +63,7 @@ "devDependencies": { "@types/js-yaml": "^4.0.9", "@types/uuid": "^10.0.0", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" @@ -16365,21 +16365,21 @@ }, "packages/cli": { "name": "@zowe/cli", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "hasInstallScript": true, "license": "EPL-2.0", "dependencies": { - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809", - "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202408301809", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603", + "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603", "find-process": "1.4.7", "lodash": "4.17.21", "minimatch": "9.0.5", @@ -16392,7 +16392,7 @@ "@types/diff": "^5.0.9", "@types/lodash": "^4.17.6", "@types/tar": "^6.1.11", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", + "@zowe/cli-test-utils": "8.0.0-next.202409091603", "comment-json": "^4.2.3", "strip-ansi": "^6.0.1", "which": "^4.0.0" @@ -16401,7 +16401,7 @@ "node": ">=18.12.0" }, "optionalDependencies": { - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603" } }, "packages/cli/node_modules/brace-expansion": { @@ -16448,15 +16448,15 @@ }, "packages/core": { "name": "@zowe/core-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "comment-json": "~4.2.3", "string-width": "^4.2.3" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16467,7 +16467,7 @@ }, "packages/imperative": { "name": "@zowe/imperative", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "@types/yargs": "^17.0.32", @@ -16520,7 +16520,7 @@ "@types/pacote": "^11.1.8", "@types/progress": "^2.0.7", "@types/stack-trace": "^0.0.33", - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202408301809", + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603", "concurrently": "^8.0.0", "cowsay": "^1.6.0", "deep-diff": "^1.0.0", @@ -16661,16 +16661,16 @@ }, "packages/provisioning": { "name": "@zowe/provisioning-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "js-yaml": "^4.1.0" }, "devDependencies": { "@types/js-yaml": "^4.0.9", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16682,7 +16682,7 @@ }, "packages/secrets": { "name": "@zowe/secrets-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "hasInstallScript": true, "license": "EPL-2.0", "devDependencies": { @@ -16695,15 +16695,15 @@ }, "packages/workflows": { "name": "@zowe/zos-workflows-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16715,12 +16715,12 @@ }, "packages/zosconsole": { "name": "@zowe/zos-console-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16732,16 +16732,16 @@ }, "packages/zosfiles": { "name": "@zowe/zos-files-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "minimatch": "^9.0.5" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16773,15 +16773,15 @@ }, "packages/zosjobs": { "name": "@zowe/zos-jobs-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16793,12 +16793,12 @@ }, "packages/zoslogs": { "name": "@zowe/zos-logs-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16810,12 +16810,12 @@ }, "packages/zosmf": { "name": "@zowe/zosmf-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16827,15 +16827,15 @@ }, "packages/zostso": { "name": "@zowe/zos-tso-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" @@ -16847,15 +16847,15 @@ }, "packages/zosuss": { "name": "@zowe/zos-uss-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "license": "EPL-2.0", "dependencies": { "ssh2": "^1.15.0" }, "devDependencies": { "@types/ssh2": "^1.11.19", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" diff --git a/packages/cli/package.json b/packages/cli/package.json index 2a12662d1..ef2d08a4d 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/cli", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "zoweVersion": "v3.0.0-prerelease", "description": "Zowe CLI is a command line interface (CLI) that provides a simple and streamlined way to interact with IBM z/OS.", "author": "Zowe", @@ -58,17 +58,17 @@ "preshrinkwrap": "node ../../scripts/rewriteShrinkwrap.js" }, "dependencies": { - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809", - "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202408301809", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603", + "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603", "find-process": "1.4.7", "lodash": "4.17.21", "minimatch": "9.0.5", @@ -78,13 +78,13 @@ "@types/diff": "^5.0.9", "@types/lodash": "^4.17.6", "@types/tar": "^6.1.11", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", + "@zowe/cli-test-utils": "8.0.0-next.202409091603", "comment-json": "^4.2.3", "strip-ansi": "^6.0.1", "which": "^4.0.0" }, "optionalDependencies": { - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603" }, "engines": { "node": ">=18.12.0" diff --git a/packages/core/package.json b/packages/core/package.json index 06d2dbdcd..c699094dd 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/core-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Core libraries shared by Zowe SDK packages", "author": "Zowe", "license": "EPL-2.0", @@ -49,8 +49,8 @@ "string-width": "^4.2.3" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" diff --git a/packages/imperative/package.json b/packages/imperative/package.json index 2b337b056..90db2fa50 100644 --- a/packages/imperative/package.json +++ b/packages/imperative/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/imperative", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "framework for building configurable CLIs", "author": "Zowe", "license": "EPL-2.0", @@ -95,7 +95,7 @@ "@types/pacote": "^11.1.8", "@types/progress": "^2.0.7", "@types/stack-trace": "^0.0.33", - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202408301809", + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603", "concurrently": "^8.0.0", "cowsay": "^1.6.0", "deep-diff": "^1.0.0", diff --git a/packages/provisioning/package.json b/packages/provisioning/package.json index ec7b0534e..a2e46c594 100644 --- a/packages/provisioning/package.json +++ b/packages/provisioning/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/provisioning-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with the z/OS provisioning APIs", "author": "Zowe", "license": "EPL-2.0", @@ -49,9 +49,9 @@ }, "devDependencies": { "@types/js-yaml": "^4.0.9", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/secrets/package.json b/packages/secrets/package.json index 1fe56608c..a4e70ac50 100644 --- a/packages/secrets/package.json +++ b/packages/secrets/package.json @@ -3,7 +3,7 @@ "description": "Credential management facilities for Imperative, Zowe CLI, and extenders.", "repository": "https://github.com/zowe/zowe-cli.git", "author": "Zowe", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "homepage": "https://github.com/zowe/zowe-cli/tree/master/packages/secrets#readme", "bugs": { "url": "https://github.com/zowe/zowe-cli/issues" diff --git a/packages/workflows/package.json b/packages/workflows/package.json index 464996147..1621dd9d5 100644 --- a/packages/workflows/package.json +++ b/packages/workflows/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-workflows-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with the z/OS workflows APIs", "author": "Zowe", "license": "EPL-2.0", @@ -45,12 +45,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosconsole/package.json b/packages/zosconsole/package.json index 6fc0c2033..76bf41256 100644 --- a/packages/zosconsole/package.json +++ b/packages/zosconsole/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-console-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with the z/OS console", "author": "Zowe", "license": "EPL-2.0", @@ -45,9 +45,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosfiles/package.json b/packages/zosfiles/package.json index 44c77c09b..3f02343ef 100644 --- a/packages/zosfiles/package.json +++ b/packages/zosfiles/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-files-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with files and data sets on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -49,10 +49,10 @@ "minimatch": "^9.0.5" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosjobs/package.json b/packages/zosjobs/package.json index f954e843a..db84cab22 100644 --- a/packages/zosjobs/package.json +++ b/packages/zosjobs/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-jobs-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with jobs on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -46,12 +46,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zoslogs/package.json b/packages/zoslogs/package.json index 8f5ed0cac..b5c1234fa 100644 --- a/packages/zoslogs/package.json +++ b/packages/zoslogs/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-logs-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with the z/OS logs", "author": "Zowe", "license": "EPL-2.0", @@ -45,9 +45,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosmf/package.json b/packages/zosmf/package.json index 0c7283dc4..00da6ba5d 100644 --- a/packages/zosmf/package.json +++ b/packages/zosmf/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zosmf-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with the z/OS Management Facility", "author": "Zowe", "license": "EPL-2.0", @@ -44,9 +44,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zostso/package.json b/packages/zostso/package.json index 1a44c07d5..a39420c07 100644 --- a/packages/zostso/package.json +++ b/packages/zostso/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-tso-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with TSO on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -45,12 +45,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202408301809" + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosuss/package.json b/packages/zosuss/package.json index 195dcd7a5..85cc10e53 100644 --- a/packages/zosuss/package.json +++ b/packages/zosuss/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-uss-for-zowe-sdk", - "version": "8.0.0-next.202408301809", + "version": "8.0.0-next.202409091603", "description": "Zowe SDK to interact with USS on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -49,8 +49,8 @@ }, "devDependencies": { "@types/ssh2": "^1.11.19", - "@zowe/cli-test-utils": "8.0.0-next.202408301809", - "@zowe/imperative": "8.0.0-next.202408301809" + "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/imperative": "8.0.0-next.202409091603" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" From c706362992afb9958da9ec6225b0089a5645c4a1 Mon Sep 17 00:00:00 2001 From: "Andrew W. Harn" Date: Wed, 11 Sep 2024 10:08:21 -0400 Subject: [PATCH 13/14] Ignore warning for unmaintained component Signed-off-by: Andrew W. Harn --- .github/workflows/audit.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/audit.yml b/.github/workflows/audit.yml index 12bd5c949..63d93d2f9 100644 --- a/.github/workflows/audit.yml +++ b/.github/workflows/audit.yml @@ -37,4 +37,4 @@ jobs: - name: Check Secrets SDK Vulnerabilities working-directory: packages/secrets/src/keyring - run: cargo audit --deny warnings + run: cargo audit --deny warnings --ignore RUSTSEC-2024-0370 From 024d0dccb653ab6ca2784d943088ce5d89b2497a Mon Sep 17 00:00:00 2001 From: zowe-robot Date: Wed, 11 Sep 2024 15:28:44 +0000 Subject: [PATCH 14/14] Bump version to 8.0.0-next.202409111528 [ci skip] Signed-off-by: zowe-robot --- .../__packages__/cli-test-utils/package.json | 4 +- lerna.json | 2 +- npm-shrinkwrap.json | 122 +++++++++--------- packages/cli/package.json | 28 ++-- packages/core/package.json | 6 +- packages/imperative/package.json | 4 +- packages/provisioning/package.json | 8 +- packages/secrets/package.json | 2 +- packages/workflows/package.json | 10 +- packages/zosconsole/package.json | 8 +- packages/zosfiles/package.json | 10 +- packages/zosjobs/package.json | 10 +- packages/zoslogs/package.json | 8 +- packages/zosmf/package.json | 8 +- packages/zostso/package.json | 10 +- packages/zosuss/package.json | 6 +- 16 files changed, 123 insertions(+), 123 deletions(-) diff --git a/__tests__/__packages__/cli-test-utils/package.json b/__tests__/__packages__/cli-test-utils/package.json index 21dbd7e33..9572afc71 100644 --- a/__tests__/__packages__/cli-test-utils/package.json +++ b/__tests__/__packages__/cli-test-utils/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/cli-test-utils", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Test utilities package for Zowe CLI plug-ins", "author": "Zowe", "license": "EPL-2.0", @@ -43,7 +43,7 @@ "devDependencies": { "@types/js-yaml": "^4.0.9", "@types/uuid": "^10.0.0", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" diff --git a/lerna.json b/lerna.json index c927a051e..c581f3045 100644 --- a/lerna.json +++ b/lerna.json @@ -1,5 +1,5 @@ { - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "command": { "publish": { "ignoreChanges": [ diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json index fbe1f8c51..b111e1868 100644 --- a/npm-shrinkwrap.json +++ b/npm-shrinkwrap.json @@ -52,7 +52,7 @@ }, "__tests__/__packages__/cli-test-utils": { "name": "@zowe/cli-test-utils", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "find-up": "^5.0.0", @@ -63,7 +63,7 @@ "devDependencies": { "@types/js-yaml": "^4.0.9", "@types/uuid": "^10.0.0", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" @@ -16365,21 +16365,21 @@ }, "packages/cli": { "name": "@zowe/cli", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "hasInstallScript": true, "license": "EPL-2.0", "dependencies": { - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603", - "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528", + "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409111528", "find-process": "1.4.7", "lodash": "4.17.21", "minimatch": "9.0.5", @@ -16392,7 +16392,7 @@ "@types/diff": "^5.0.9", "@types/lodash": "^4.17.6", "@types/tar": "^6.1.11", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/cli-test-utils": "8.0.0-next.202409111528", "comment-json": "^4.2.3", "strip-ansi": "^6.0.1", "which": "^4.0.0" @@ -16401,7 +16401,7 @@ "node": ">=18.12.0" }, "optionalDependencies": { - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409111528" } }, "packages/cli/node_modules/brace-expansion": { @@ -16448,15 +16448,15 @@ }, "packages/core": { "name": "@zowe/core-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "comment-json": "~4.2.3", "string-width": "^4.2.3" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16467,7 +16467,7 @@ }, "packages/imperative": { "name": "@zowe/imperative", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "@types/yargs": "^17.0.32", @@ -16520,7 +16520,7 @@ "@types/pacote": "^11.1.8", "@types/progress": "^2.0.7", "@types/stack-trace": "^0.0.33", - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409111528", "concurrently": "^8.0.0", "cowsay": "^1.6.0", "deep-diff": "^1.0.0", @@ -16661,16 +16661,16 @@ }, "packages/provisioning": { "name": "@zowe/provisioning-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "js-yaml": "^4.1.0" }, "devDependencies": { "@types/js-yaml": "^4.0.9", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16682,7 +16682,7 @@ }, "packages/secrets": { "name": "@zowe/secrets-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "hasInstallScript": true, "license": "EPL-2.0", "devDependencies": { @@ -16695,15 +16695,15 @@ }, "packages/workflows": { "name": "@zowe/zos-workflows-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16715,12 +16715,12 @@ }, "packages/zosconsole": { "name": "@zowe/zos-console-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16732,16 +16732,16 @@ }, "packages/zosfiles": { "name": "@zowe/zos-files-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "minimatch": "^9.0.5" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16773,15 +16773,15 @@ }, "packages/zosjobs": { "name": "@zowe/zos-jobs-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16793,12 +16793,12 @@ }, "packages/zoslogs": { "name": "@zowe/zos-logs-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16810,12 +16810,12 @@ }, "packages/zosmf": { "name": "@zowe/zosmf-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16827,15 +16827,15 @@ }, "packages/zostso": { "name": "@zowe/zos-tso-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" @@ -16847,15 +16847,15 @@ }, "packages/zosuss": { "name": "@zowe/zos-uss-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "license": "EPL-2.0", "dependencies": { "ssh2": "^1.15.0" }, "devDependencies": { "@types/ssh2": "^1.11.19", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" diff --git a/packages/cli/package.json b/packages/cli/package.json index ef2d08a4d..2fb795b31 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/cli", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "zoweVersion": "v3.0.0-prerelease", "description": "Zowe CLI is a command line interface (CLI) that provides a simple and streamlined way to interact with IBM z/OS.", "author": "Zowe", @@ -58,17 +58,17 @@ "preshrinkwrap": "node ../../scripts/rewriteShrinkwrap.js" }, "dependencies": { - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603", - "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528", + "@zowe/provisioning-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-console-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-jobs-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-logs-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-tso-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zos-workflows-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409111528", "find-process": "1.4.7", "lodash": "4.17.21", "minimatch": "9.0.5", @@ -78,13 +78,13 @@ "@types/diff": "^5.0.9", "@types/lodash": "^4.17.6", "@types/tar": "^6.1.11", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", + "@zowe/cli-test-utils": "8.0.0-next.202409111528", "comment-json": "^4.2.3", "strip-ansi": "^6.0.1", "which": "^4.0.0" }, "optionalDependencies": { - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409111528" }, "engines": { "node": ">=18.12.0" diff --git a/packages/core/package.json b/packages/core/package.json index c699094dd..1526dd8d4 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/core-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Core libraries shared by Zowe SDK packages", "author": "Zowe", "license": "EPL-2.0", @@ -49,8 +49,8 @@ "string-width": "^4.2.3" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next" diff --git a/packages/imperative/package.json b/packages/imperative/package.json index 90db2fa50..ab2af6e5d 100644 --- a/packages/imperative/package.json +++ b/packages/imperative/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/imperative", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "framework for building configurable CLIs", "author": "Zowe", "license": "EPL-2.0", @@ -95,7 +95,7 @@ "@types/pacote": "^11.1.8", "@types/progress": "^2.0.7", "@types/stack-trace": "^0.0.33", - "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409091603", + "@zowe/secrets-for-zowe-sdk": "8.0.0-next.202409111528", "concurrently": "^8.0.0", "cowsay": "^1.6.0", "deep-diff": "^1.0.0", diff --git a/packages/provisioning/package.json b/packages/provisioning/package.json index a2e46c594..e0e0ffd98 100644 --- a/packages/provisioning/package.json +++ b/packages/provisioning/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/provisioning-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with the z/OS provisioning APIs", "author": "Zowe", "license": "EPL-2.0", @@ -49,9 +49,9 @@ }, "devDependencies": { "@types/js-yaml": "^4.0.9", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/secrets/package.json b/packages/secrets/package.json index a4e70ac50..800d59e57 100644 --- a/packages/secrets/package.json +++ b/packages/secrets/package.json @@ -3,7 +3,7 @@ "description": "Credential management facilities for Imperative, Zowe CLI, and extenders.", "repository": "https://github.com/zowe/zowe-cli.git", "author": "Zowe", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "homepage": "https://github.com/zowe/zowe-cli/tree/master/packages/secrets#readme", "bugs": { "url": "https://github.com/zowe/zowe-cli/issues" diff --git a/packages/workflows/package.json b/packages/workflows/package.json index 1621dd9d5..092aeed8f 100644 --- a/packages/workflows/package.json +++ b/packages/workflows/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-workflows-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with the z/OS workflows APIs", "author": "Zowe", "license": "EPL-2.0", @@ -45,12 +45,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosconsole/package.json b/packages/zosconsole/package.json index 76bf41256..31ed4b40d 100644 --- a/packages/zosconsole/package.json +++ b/packages/zosconsole/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-console-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with the z/OS console", "author": "Zowe", "license": "EPL-2.0", @@ -45,9 +45,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosfiles/package.json b/packages/zosfiles/package.json index 3f02343ef..9c5c20c9f 100644 --- a/packages/zosfiles/package.json +++ b/packages/zosfiles/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-files-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with files and data sets on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -49,10 +49,10 @@ "minimatch": "^9.0.5" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603", - "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528", + "@zowe/zos-uss-for-zowe-sdk": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosjobs/package.json b/packages/zosjobs/package.json index db84cab22..3656b6955 100644 --- a/packages/zosjobs/package.json +++ b/packages/zosjobs/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-jobs-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with jobs on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -46,12 +46,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zos-files-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zoslogs/package.json b/packages/zoslogs/package.json index b5c1234fa..d4ba523fd 100644 --- a/packages/zoslogs/package.json +++ b/packages/zoslogs/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-logs-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with the z/OS logs", "author": "Zowe", "license": "EPL-2.0", @@ -45,9 +45,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosmf/package.json b/packages/zosmf/package.json index 00da6ba5d..fbfdfc80d 100644 --- a/packages/zosmf/package.json +++ b/packages/zosmf/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zosmf-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with the z/OS Management Facility", "author": "Zowe", "license": "EPL-2.0", @@ -44,9 +44,9 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zostso/package.json b/packages/zostso/package.json index a39420c07..f079469c6 100644 --- a/packages/zostso/package.json +++ b/packages/zostso/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-tso-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with TSO on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -45,12 +45,12 @@ "prepack": "node ../../scripts/prepareLicenses.js" }, "dependencies": { - "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409091603" + "@zowe/zosmf-for-zowe-sdk": "8.0.0-next.202409111528" }, "devDependencies": { - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/core-for-zowe-sdk": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/core-for-zowe-sdk": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/core-for-zowe-sdk": "^8.0.0-next", diff --git a/packages/zosuss/package.json b/packages/zosuss/package.json index 85cc10e53..2260158b4 100644 --- a/packages/zosuss/package.json +++ b/packages/zosuss/package.json @@ -1,6 +1,6 @@ { "name": "@zowe/zos-uss-for-zowe-sdk", - "version": "8.0.0-next.202409091603", + "version": "8.0.0-next.202409111528", "description": "Zowe SDK to interact with USS on z/OS", "author": "Zowe", "license": "EPL-2.0", @@ -49,8 +49,8 @@ }, "devDependencies": { "@types/ssh2": "^1.11.19", - "@zowe/cli-test-utils": "8.0.0-next.202409091603", - "@zowe/imperative": "8.0.0-next.202409091603" + "@zowe/cli-test-utils": "8.0.0-next.202409111528", + "@zowe/imperative": "8.0.0-next.202409111528" }, "peerDependencies": { "@zowe/imperative": "^8.0.0-next"