diff --git a/.github/workflows/manifest_updateVersions.createPR.yml b/.github/workflows/manifest_updateVersions.createPR.yml index 0c2437d..6ba53c4 100644 --- a/.github/workflows/manifest_updateVersions.createPR.yml +++ b/.github/workflows/manifest_updateVersions.createPR.yml @@ -33,6 +33,7 @@ jobs: with: repository: 'zowe/zowe-install-packaging' ref: ${{ env.defaultBranch }} + token: ${{ secrets.ZOWE_ROBOT_TOKEN }} - name: Set up Node.js uses: actions/setup-node@v3 @@ -48,11 +49,10 @@ jobs: id: get_versions run: | declare -A repoAndComponent - repoAndComponent[imperative]=imperative repoAndComponent[cli]=zowe-cli repoAndComponent[cics-for-zowe-cli]=zowe-cli-cics-plugin repoAndComponent[db2-for-zowe-cli]=zowe-cli-db2-plugin - repoAndComponent[perf-timing]=perf-timing + repoAndComponent[ims-for-zowe-cli]=zowe-cli-ims-plugin repoAndComponent[mq-for-zowe-cli]=zowe-cli-mq-plugin repoAndComponent[zos-ftp-for-zowe-cli]=zowe-cli-ftp-plugin @@ -68,9 +68,9 @@ jobs: for component in "${!repoAndComponent[@]}"; do repo="${repoAndComponent[$component]}" current_version=$(grep -A 2 "\"repository\": \"$repo\"" manifest.json.template | awk -F '"' '/"tag":/ {print $4}') - new_version=v$(npm view @zowe/$component "dist-tags.$zowe_version") + new_version=v$(npm view @zowe/$component "dist-tags.$zowe_version" --@zowe:registry=https://zowe.jfrog.io/zowe/api/npm/npm-local-release/) if [[ "$new_version" != "$current_version" ]]; then - echo "|$component | $current_version | $new_version|" >> description.txt + echo "| $component | $current_version | $new_version |" >> description.txt # Replaces the version number. If it doesn't match on the first line after the component, it goes to the next line and checks again. sed -i -E "/\"repository\": \"$repo\"/{n;s/(\"tag\": \").*(\",)/\1$new_version\2/}" manifest.json.template fi @@ -78,19 +78,19 @@ jobs: - name: Commit and Push Changes run: | - git config --global user.name "GitHub Actions" - git config --global user.email "actions@github.com" + git config --global user.name ${{ secrets.ZOWE_ROBOT_USER }} + git config --global user.email ${{ secrets.ZOWE_ROBOT_EMAIL }} git add "manifest.json.template" - git commit -m "Update component versions" + git commit -sm "Update component versions" git push origin HEAD - name: Create Pull Request run: | version="${{ github.event.inputs.version }}" branch_name="v$version/cli/rc" - pr_title="Update versions for $version" + pr_title="Update CLI component versions for $version" body_file=description.txt - gh pr create --base ${{ env.defaultBranch }} --head "$branch_name" --title "$pr_title" --body-file "$body_file" --reviewer atorrise + gh pr create --base ${{ env.defaultBranch }} --head "$branch_name" --title "$pr_title" --body-file "$body_file" --reviewer ojcelis,MarkAckert echo "Pull Request created successfully" env: GH_TOKEN: ${{ secrets.ZOWE_ROBOT_TOKEN }} diff --git a/.github/workflows/zowe-versions_updateVersions_createPR.yml b/.github/workflows/zowe-versions_updateVersions_createPR.yml index ccae584..13e5fcc 100644 --- a/.github/workflows/zowe-versions_updateVersions_createPR.yml +++ b/.github/workflows/zowe-versions_updateVersions_createPR.yml @@ -1,85 +1,85 @@ -name: Update Versions and Create PR (zowe-versions) - -on: - workflow_dispatch: - inputs: - version: - description: 'Release Version (x.x.x)' - required: true - zowe_version: - description: "Zowe Version Tag" - default: zowe-v2-lts - required: true - type: choice - options: - - zowe-v1-lts - - zowe-v2-lts - -jobs: - update_versions_and_create_pr: - runs-on: ubuntu-latest - - steps: - - name: Checkout Repository - uses: actions/checkout@v3 - - - name: Set up Node.js - uses: actions/setup-node@v3 - with: - node-version: lts/* - - - name: Create Branch - run: | - version_name="${{ github.event.inputs.version }}" - branch_name="v$version_name/master" - git checkout -b "$branch_name" - - - name: Get and Change Component Versions - id: get_versions - run: | - zowe_version="${{ github.event.inputs.zowe_version }}" - components=$(yq -r ".packages | with_entries(select(.value.\"$zowe_version\")) | keys | .[]" zowe-versions.yaml) - version="${{ github.event.inputs.version }}" - # echoing to txt file to later add this file as the PR description - echo "This PR updates the following package versions in zowe-versions.yaml for \`$zowe_version\`" >> description.txt - echo "| Updated Package | Old Version | New Version |" >> description.txt - echo "| --- | --- | --- |" >> description.txt - for component in $components; do - current_version=$(grep -A 2 "^ $component:" zowe-versions.yaml | grep "$zowe_version" | awk '{print $2}' | tr -d '\r') - new_version=$(npm view @zowe/$component "dist-tags.$zowe_version") - if [[ "$new_version" != "$current_version" ]]; then - echo "|$component | $current_version | $new_version|" >> description.txt - # Replaces the version number. If it doesn't match on the first line after the component, it goes to the next line and checks again. - sed -i -E "/^ $component:/ { n; s/($zowe_version: ).*/\1$new_version/; t; n; s/($zowe_version: ).*/\1$new_version/ }" zowe-versions.yaml - fi - done - - # Update zowe-versions.yaml tags section (always sets rc = 1) - sed -i -E "/$zowe_version:/ { n; s/(version: ).*/\1$version/; s/(rc: )[0-9]+/\11/ }" zowe-versions.yaml - - - - name: Commit and Push Changes - run: | - git config --global user.name "GitHub Actions" - git config --global user.email "actions@github.com" - git add zowe-versions.yaml - git commit -sm "Update component versions" - git push origin HEAD - - - name: Create Pull Request - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - run: | - version_name="${{ github.event.inputs.version }}" - branch_name="v$version_name/master" - pr_title="Update zowe component versions for $version_name" - body_file=description.txt - pr_url=$(gh pr create --base master --head "$branch_name" --title "$pr_title" --body-file "$body_file") - pr_number=$(echo "$pr_url" | sed 's/.*\/\([0-9]\+\)$/\1/') - curl -X POST \ - -H "Accept: application/vnd.github+json" \ - -H "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}"\ - https://api.github.com/repos/zowe/zowe-cli-standalone-package/pulls/$pr_number/requested_reviewers \ - -d '{"team_reviewers":["zowe-cli-administrators"]}' - - echo "Pull Request created successfully" +name: Update Versions and Create PR (zowe-versions) + +on: + workflow_dispatch: + inputs: + version: + description: 'Release Version (x.x.x)' + required: true + zowe_version: + description: "Zowe Version Tag" + default: zowe-v2-lts + required: true + type: choice + options: + - zowe-v1-lts + - zowe-v2-lts + +jobs: + update_versions_and_create_pr: + runs-on: ubuntu-latest + + steps: + - name: Checkout Repository + uses: actions/checkout@v3 + + - name: Set up Node.js + uses: actions/setup-node@v3 + with: + node-version: lts/* + + - name: Create Branch + run: | + version_name="${{ github.event.inputs.version }}" + branch_name="v$version_name/master" + git checkout -b "$branch_name" + + - name: Get and Change Component Versions + id: get_versions + run: | + zowe_version="${{ github.event.inputs.zowe_version }}" + components=$(yq -r ".packages | with_entries(select(.value.\"$zowe_version\")) | keys | .[]" zowe-versions.yaml) + version="${{ github.event.inputs.version }}" + # echoing to txt file to later add this file as the PR description + echo "This PR updates the following package versions in zowe-versions.yaml for \`$zowe_version\`" >> description.txt + echo "| Updated Package | Old Version | New Version |" >> description.txt + echo "| --- | --- | --- |" >> description.txt + for component in $components; do + current_version=$(grep -A 2 "^ $component:" zowe-versions.yaml | grep "$zowe_version" | awk '{print $2}' | tr -d '\r') + new_version=$(npm view @zowe/$component "dist-tags.$zowe_version" --@zowe:registry=https://zowe.jfrog.io/zowe/api/npm/npm-local-release/) + if [[ "$new_version" != "$current_version" ]]; then + echo "| $component | $current_version | $new_version |" >> description.txt + # Replaces the version number. If it doesn't match on the first line after the component, it goes to the next line and checks again. + sed -i -E "/^ $component:/ { n; s/($zowe_version: ).*/\1$new_version/; t; n; s/($zowe_version: ).*/\1$new_version/ }" zowe-versions.yaml + fi + done + + # Update zowe-versions.yaml tags section (always sets rc = 1) + sed -i -E "/$zowe_version:/ { n; s/(version: ).*/\1$version/; s/(rc: )[0-9]+/\11/ }" zowe-versions.yaml + + + - name: Commit and Push Changes + run: | + git config --global user.name ${{ secrets.ZOWE_ROBOT_USER }} + git config --global user.email ${{ secrets.ZOWE_ROBOT_EMAIL }} + git add zowe-versions.yaml + git commit -sm "Update component versions" + git push origin HEAD + + - name: Create Pull Request + env: + GH_TOKEN: ${{ secrets.ZOWE_ROBOT_TOKEN }} + run: | + version_name="${{ github.event.inputs.version }}" + branch_name="v$version_name/master" + pr_title="Update zowe component versions for $version_name" + body_file=description.txt + pr_url=$(gh pr create --base master --head "$branch_name" --title "$pr_title" --body-file "$body_file") + pr_number=$(echo "$pr_url" | sed 's/.*\/\([0-9]\+\)$/\1/') + curl -X POST \ + -H "Accept: application/vnd.github+json" \ + -H "Authorization: Bearer ${{ secrets.ZOWE_ROBOT_TOKEN }}"\ + https://api.github.com/repos/zowe/zowe-cli-standalone-package/pulls/$pr_number/requested_reviewers \ + -d '{"team_reviewers":["zowe-cli-administrators"]}' + + echo "Pull Request created successfully" diff --git a/README.md b/README.md index d3f42ff..6151e47 100755 --- a/README.md +++ b/README.md @@ -1,82 +1,82 @@ -# Zowe CLI Standalone Package Pipeline - -This repository pulls the latest Zowe CLI and Zowe CLI Plugin Artifacts from Artifactory, and generates a standalone ZIP file containing the contents. - -The standalone ZIP is intended to be offline-installable for those users who are unable to connect to public NPM registries. The Zowe CLI DB2 Plugin is the lone exception, as this plugin has dependencies on ODBC drivers and DDB licenses which much be obtained by users separately. See the official Zowe Documentation for more information. - -## Steps prior to a Zowe Release - -Before every Zowe release goes GA, we need to align with the code freeze dates and produce snapshots to be promoted to RCs later in the process. Follow the steps below to accomplish that. - -1. Create a PR into `master` with the following changes and information: - - Update release number to match the RC that's going out (e.g. 1.22.0) - - Update any packages that changed after the last Zowe Release. - - Add a summary of the changes in the PR description like below: - | Updated Packages | Old Version | New Version | - | --- | --- | --- | - | Imperative | 4.13.0 | 4.13.1 | - | Zowe CLI and SDKs | 6.31.0 | 6.31.1 | - | z/OS USS SDK for Zowe CLI | 6.30.0 | 6.31.1 | - | SCS plug-in for Zowe CLI | 4.1.3 | 4.1.5 | - | z/OS FTP plug-in for Zowe CLI | 1.4.1 | 1.6.0 | -2. Check to see if the `master` build failed due to missing licenses. - - If so, rerun the workflow and change the license URL to a previous version -3. Notify `Tom Zhang` on Slack and make sure to copy a link to the PR and the build that uploaded the bundles to `libs-snapshot-local` on JFrog Artifactory -4. After the RC is approved and the license zip is available, we need to update the licenses URL to the Zowe version that's about to go GA. -5. After the Zowe Release is GA, create a new branch with the version corresponding to that of the Zowe Release. - -## Nightly Deployment - -This repository contains a GitHub workflow that runs every night to mirror @zowe-scoped packages from Artifactory to npmjs.org. The list of packages to deploy is defined in zowe-versions.yaml. - -To deploy an individual package, run the workflow zowe-cli-deploy-component.yaml. Specify the package name without the scope (e.g., `core-for-zowe-sdk`) and a space-separated list of tags to publish (e.g., `latest next`). - -When a Zowe release has been staged but is not yet GA, it is expected that the Zowe bundle version hosted on zowe.org and the version defined in zowe-versions.yaml@master will differ. During this period, the workflow runs in "staging mode" which means that: -* Packages with "next" tag are not published if their date is newer than the snapshot date defined in zowe-versions.yaml -* Packages with other tags are not published if their version is newer than the one defined in zowe-versions.yaml - * For the "latest" tag, it is assumed that the 1st tag listed for a package in zowe-versions.yaml is aliased with @latest - -Packages defined in the "extras" section of zowe-versions.yaml will always be published and are unaffected by staging mode since they are not included in Zowe CLI bundles. - -## External Packages - -If you develop a Zowe CLI plug-in that meets the following criteria: -* External - not included in the Zowe CLI bundle -* Sourced in a repository under the Zowe GitHub organization -* Already deploys and tags new releases on Zowe Artifactory -* Authorized to publish to npmjs.org under the `@zowe` scope - -Then you can follow these steps to automate publishing your plug-in to NPM: -1. Fork this repository and create a pull request that adds your package to the `extras` section of [zowe-versions.yaml](./zowe-versions.yaml). For example, to publish `@zowe/sample-plugin-for-zowe-cli`: - ```yaml - extras: - sample-plugin-for-zowe-cli: - zowe-v1-lts: true - zowe-v2-lts: true - ``` - This enables nightly automation to publish the "latest" (included by default), "zowe-v1-lts", and "zowe-v2-lts" tags. The list of tags should match the ones you want to publish for your plug-in. -2. (optional) In your plug-in's repository, add the following GitHub workflow: - ```yaml - name: Publish to NPM - - on: - workflow_dispatch: - inputs: - pkg-tags: - description: "Tags to be distributed from Artifactory (separate multiple by spaces)" - default: "latest" - required: true - - jobs: - publish: - uses: zowe/zowe-cli-standalone-package/.github/workflows/zowe-cli-deploy-component.yaml@master - secrets: - NPM_PUBLIC_TOKEN: ${{ secrets.NPM_PUBLIC_TOKEN }} - with: - pkg-name: 'sample-plugin-for-zowe-cli' - pkg-tags: ${{ github.event.inputs.pkg-tags }} - ``` - > **Note** - > Replace "sample-plugin-for-zowe-cli" with the package name of your plug-in (without the `@zowe` prefix). - - This workflow can be run on demand to immediately publish your plug-in to NPM if the nightly automation is not adequate. +# Zowe CLI Standalone Package Pipeline + +This repository pulls the latest Zowe CLI and Zowe CLI Plugin Artifacts from Artifactory, and generates a standalone ZIP file containing the contents. + +The standalone ZIP is intended to be offline-installable for those users who are unable to connect to public NPM registries. The Zowe CLI DB2 Plugin is the lone exception, as this plugin has dependencies on ODBC drivers and DDB licenses which much be obtained by users separately. See the official Zowe Documentation for more information. + +## Steps prior to a Zowe Release + +Before every Zowe release goes GA, we need to align with the code freeze dates and produce snapshots to be promoted to RCs later in the process. Follow the steps below to accomplish that. + +1. Create a PR into `master` with the following changes and information: + - Update release number to match the RC that's going out (e.g. 1.22.0) + - Update any packages that changed after the last Zowe Release. + - Add a summary of the changes in the PR description like below: + | Updated Packages | Old Version | New Version | + | --- | --- | --- | + | Imperative | 4.13.0 | 4.13.1 | + | Zowe CLI and SDKs | 6.31.0 | 6.31.1 | + | z/OS USS SDK for Zowe CLI | 6.30.0 | 6.31.1 | + | SCS plug-in for Zowe CLI | 4.1.3 | 4.1.5 | + | z/OS FTP plug-in for Zowe CLI | 1.4.1 | 1.6.0 | +2. Check to see if the `master` build failed due to missing licenses. + - If so, rerun the workflow and change the license URL to a previous version +3. Notify `Tom Zhang` on Slack and make sure to copy a link to the PR and the build that uploaded the bundles to `libs-snapshot-local` on JFrog Artifactory +4. After the RC is approved and the license zip is available, we need to update the licenses URL to the Zowe version that's about to go GA. +5. After the Zowe Release is GA, create a new branch with the version corresponding to that of the Zowe Release. + +## Nightly Deployment + +This repository contains a GitHub workflow that runs every night to mirror @zowe-scoped packages from Artifactory to npmjs.org. The list of packages to deploy is defined in zowe-versions.yaml. + +To deploy an individual package, run the workflow zowe-cli-deploy-component.yaml. Specify the package name without the scope (e.g., `core-for-zowe-sdk`) and a space-separated list of tags to publish (e.g., `latest next`). + +When a Zowe release has been staged but is not yet GA, it is expected that the Zowe bundle version hosted on zowe.org and the version defined in zowe-versions.yaml@master will differ. During this period, the workflow runs in "staging mode" which means that: +* Packages with "next" tag are not published if their date is newer than the snapshot date defined in zowe-versions.yaml +* Packages with other tags are not published if their version is newer than the one defined in zowe-versions.yaml + * For the "latest" tag, it is assumed that the 1st tag listed for a package in zowe-versions.yaml is aliased with @latest + +Packages defined in the "extras" section of zowe-versions.yaml will always be published and are unaffected by staging mode since they are not included in Zowe CLI bundles. + +## External Packages + +If you develop a Zowe CLI plug-in that meets the following criteria: +* External - not included in the Zowe CLI bundle +* Sourced in a repository under the Zowe GitHub organization +* Already deploys and tags new releases on Zowe Artifactory +* Authorized to publish to npmjs.org under the `@zowe` scope + +Then you can follow these steps to automate publishing your plug-in to NPM: +1. Fork this repository and create a pull request that adds your package to the `extras` section of [zowe-versions.yaml](./zowe-versions.yaml). For example, to publish `@zowe/sample-plugin-for-zowe-cli`: + ```yaml + extras: + sample-plugin-for-zowe-cli: + zowe-v1-lts: true + zowe-v2-lts: true + ``` + This enables nightly automation to publish the "latest" (included by default), "zowe-v1-lts", and "zowe-v2-lts" tags. The list of tags should match the ones you want to publish for your plug-in. +2. (optional) In your plug-in's repository, add the following GitHub workflow: + ```yaml + name: Publish to NPM + + on: + workflow_dispatch: + inputs: + pkg-tags: + description: "Tags to be distributed from Artifactory (separate multiple by spaces)" + default: "latest" + required: true + + jobs: + publish: + uses: zowe/zowe-cli-standalone-package/.github/workflows/zowe-cli-deploy-component.yaml@master + secrets: + NPM_PUBLIC_TOKEN: ${{ secrets.NPM_PUBLIC_TOKEN }} + with: + pkg-name: 'sample-plugin-for-zowe-cli' + pkg-tags: ${{ github.event.inputs.pkg-tags }} + ``` + > **Note** + > Replace "sample-plugin-for-zowe-cli" with the package name of your plug-in (without the `@zowe` prefix). + + This workflow can be run on demand to immediately publish your plug-in to NPM if the nightly automation is not adequate. diff --git a/zowe-versions.yaml b/zowe-versions.yaml index 44bdfda..945805b 100644 --- a/zowe-versions.yaml +++ b/zowe-versions.yaml @@ -1,125 +1,125 @@ -# Define @zowe-scoped packages that are included in CLI bundles on zowe.org. -# These packages will be mirrored from Artifactory to npmjs.org nightly, unless -# there is a new Zowe release staged but not yet GA. If there is, we are in -# staging mode and package versions will be locked down (see README.md). -# -# The @latest tag is assumed for all packages and does not need to be listed -# here. If there are other tags listed, the 1st one must be an alias of the -# @latest tag. For example: -# sample-plugin-for-zowe-cli: -# zowe-v1-lts: 2.0.0 # Same version for @latest and @zowe-v1-lts -# next: true # Specify whether package has a @next prerelease tag -# -# The bundle pipeline will use the versions listed here for LTS tags, and the -# latest version for @next that is before the tags.next.snapshot date defined -# below. The nightly deployment pipeline will not use these versions at all, -# except in staging mode to determine whether it should skip publishing. -packages: - # Core CLI and SDKs - perf-timing: - zowe-v2-lts: 1.0.7 - zowe-v1-lts: 1.0.7 - next: false - imperative: - zowe-v2-lts: 5.19.0 - zowe-v1-lts: 4.18.18 - next: true - cli-test-utils: - zowe-v2-lts: 7.19.0 - next: true - secrets-for-zowe-sdk: - zowe-v2-lts: 7.18.6 - next: true - core-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - zos-uss-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - provisioning-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - zos-console-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - zos-files-for-zowe-sdk: - zowe-v2-lts: 7.20.0 - zowe-v1-lts: 6.40.19 - next: true - zos-logs-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - zosmf-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - zos-workflows-for-zowe-sdk: - zowe-v2-lts: 7.20.0 - zowe-v1-lts: 6.40.19 - next: true - zos-jobs-for-zowe-sdk: - zowe-v2-lts: 7.20.0 - zowe-v1-lts: 6.40.19 - next: true - zos-tso-for-zowe-sdk: - zowe-v2-lts: 7.19.0 - zowe-v1-lts: 6.40.19 - next: true - cli: - zowe-v2-lts: 7.20.1 - zowe-v1-lts: 6.40.19 - next: true - # CLI plug-ins - cics-for-zowe-cli: - zowe-v2-lts: 5.0.1 - zowe-v1-lts: 4.0.8 - next: true - db2-for-zowe-cli: - zowe-v2-lts: 5.0.5 - zowe-v1-lts: 4.1.9 - next: true - ims-for-zowe-cli: - zowe-v2-lts: 3.0.0 - zowe-v1-lts: 2.0.4 - next: true - mq-for-zowe-cli: - zowe-v2-lts: 3.0.1 - zowe-v1-lts: 2.0.4 - next: true - secure-credential-store-for-zowe-cli: - zowe-v1-lts: 4.1.12 - next: false - zos-ftp-for-zowe-cli: - zowe-v2-lts: 2.1.6 - zowe-v1-lts: 1.8.8 - next: true - -# Define extra @zowe-scoped packages that are not included in the Zowe bundle. -# These packages will be mirrored from Artifactory to npmjs.org nightly. -extras: - tasks-for-zowe-cli: - next: true - zos-make-for-zowe-cli: - next: true - id-federation-for-zowe-cli: - next: true - zowe-v2-lts: true - secrets-for-kubernetes-for-zowe-cli: - next: true - -# Define version info for the latest staged Zowe release. -tags: - zowe-v1-lts: - version: 1.28.5 - rc: 1 - zowe-v2-lts: - version: 2.13.0 - rc: 2 - # next: - # version: 2.0.0 - # snapshot: '2022-04-15' +# Define @zowe-scoped packages that are included in CLI bundles on zowe.org. +# These packages will be mirrored from Artifactory to npmjs.org nightly, unless +# there is a new Zowe release staged but not yet GA. If there is, we are in +# staging mode and package versions will be locked down (see README.md). +# +# The @latest tag is assumed for all packages and does not need to be listed +# here. If there are other tags listed, the 1st one must be an alias of the +# @latest tag. For example: +# sample-plugin-for-zowe-cli: +# zowe-v1-lts: 2.0.0 # Same version for @latest and @zowe-v1-lts +# next: true # Specify whether package has a @next prerelease tag +# +# The bundle pipeline will use the versions listed here for LTS tags, and the +# latest version for @next that is before the tags.next.snapshot date defined +# below. The nightly deployment pipeline will not use these versions at all, +# except in staging mode to determine whether it should skip publishing. +packages: + # Core CLI and SDKs + perf-timing: + zowe-v2-lts: 1.0.7 + zowe-v1-lts: 1.0.7 + next: false + imperative: + zowe-v2-lts: 5.19.0 + zowe-v1-lts: 4.18.18 + next: true + cli-test-utils: + zowe-v2-lts: 7.19.0 + next: true + secrets-for-zowe-sdk: + zowe-v2-lts: 7.18.6 + next: true + core-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + zos-uss-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + provisioning-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + zos-console-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + zos-files-for-zowe-sdk: + zowe-v2-lts: 7.20.0 + zowe-v1-lts: 6.40.19 + next: true + zos-logs-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + zosmf-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + zos-workflows-for-zowe-sdk: + zowe-v2-lts: 7.20.0 + zowe-v1-lts: 6.40.19 + next: true + zos-jobs-for-zowe-sdk: + zowe-v2-lts: 7.20.0 + zowe-v1-lts: 6.40.19 + next: true + zos-tso-for-zowe-sdk: + zowe-v2-lts: 7.19.0 + zowe-v1-lts: 6.40.19 + next: true + cli: + zowe-v2-lts: 7.20.1 + zowe-v1-lts: 6.40.19 + next: true + # CLI plug-ins + cics-for-zowe-cli: + zowe-v2-lts: 5.0.1 + zowe-v1-lts: 4.0.8 + next: true + db2-for-zowe-cli: + zowe-v2-lts: 5.0.5 + zowe-v1-lts: 4.1.9 + next: true + ims-for-zowe-cli: + zowe-v2-lts: 3.0.0 + zowe-v1-lts: 2.0.4 + next: true + mq-for-zowe-cli: + zowe-v2-lts: 3.0.1 + zowe-v1-lts: 2.0.4 + next: true + secure-credential-store-for-zowe-cli: + zowe-v1-lts: 4.1.12 + next: false + zos-ftp-for-zowe-cli: + zowe-v2-lts: 2.1.6 + zowe-v1-lts: 1.8.8 + next: true + +# Define extra @zowe-scoped packages that are not included in the Zowe bundle. +# These packages will be mirrored from Artifactory to npmjs.org nightly. +extras: + tasks-for-zowe-cli: + next: true + zos-make-for-zowe-cli: + next: true + id-federation-for-zowe-cli: + next: true + zowe-v2-lts: true + secrets-for-kubernetes-for-zowe-cli: + next: true + +# Define version info for the latest staged Zowe release. +tags: + zowe-v1-lts: + version: 1.28.5 + rc: 1 + zowe-v2-lts: + version: 2.13.0 + rc: 2 + # next: + # version: 2.0.0 + # snapshot: '2022-04-15'