Skip to content

publish-package-to-npm #183

publish-package-to-npm

publish-package-to-npm #183

name: publish-package-to-npm
on:
workflow_dispatch:
inputs:
code-analyzer-core:
description: Should the code-analyzer-core package be released?
type: boolean
required: false
default: false
code-analyzer-engine-api:
description: Should the code-analyzer-engine-api package be released?
type: boolean
required: false
default: false
code-analyzer-eslint8-engine:
description: Should the code-analyzer-eslint8-engine package be released?
type: boolean
required: false
default: false
code-analyzer-eslint-engine:
description: Should the code-analyzer-eslint-engine package be released?
type: boolean
required: false
default: false
code-analyzer-flow-engine:
description: Should the code-analyzer-flow-engine package be released?
type: boolean
required: false
default: false
code-analyzer-pmd-engine:
description: Should the code-analyzer-pmd-engine package be released?
type: boolean
required: false
default: false
code-analyzer-regex-engine:
description: Should the code-analyzer-regex-engine package be released?
type: boolean
required: false
default: false
code-analyzer-retirejs-engine:
description: Should the code-analyzer-retirejs-engine package be released?
type: boolean
required: false
default: false
code-analyzer-sfge-engine:
description: Should the code-analyzer-sfge-engine package be released?
type: boolean
required: false
default: false
dryrun:
description: Add --dry-run to npm publish step? (Uncheck to actually publish)
type: boolean
required: false
default: true
defaults:
run:
shell: bash
jobs:
validate-packages-as-releasable:
runs-on: macos-latest
outputs:
packages-to-release: ${{ steps.main.outputs.packages_to_release }}
steps:
- name: Support long paths
run: git config --global core.longpaths true
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 'lts/*'
- name: Verify to-be-released packages are SNAPSHOT-versioned
id: main
run: |
PACKAGES_TO_CHECK_ARR=()
# ENGINE API GETS CHECKED FIRST, BECAUSE IT MUST PUBLISH FIRST
if [ "${{ inputs.code-analyzer-engine-api }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-engine-api')
fi
if [ "${{ inputs.code-analyzer-core }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-core')
fi
# NOTE: eslint8-engine MUST GET PUBLISHED BEFORE eslint-engine DUE TO THE DEPENDENCY
if [ "${{ inputs.code-analyzer-eslint8-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-eslint8-engine')
fi
if [ "${{ inputs.code-analyzer-eslint-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-eslint-engine')
fi
if [ "${{ inputs.code-analyzer-flow-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-flow-engine')
fi
if [ "${{ inputs.code-analyzer-pmd-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-pmd-engine')
fi
if [ "${{ inputs.code-analyzer-regex-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-regex-engine')
fi
if [ "${{ inputs.code-analyzer-retirejs-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-retirejs-engine')
fi
if [ "${{ inputs.code-analyzer-sfge-engine }}" == "true" ]; then
PACKAGES_TO_CHECK_ARR+=('code-analyzer-sfge-engine')
fi
PACKAGES_TO_CHECK_STR=$(IFS=' '; echo "${PACKAGES_TO_CHECK_ARR[*]}")
node ./.github/workflows/publish-package-to-npm/validate-packages-as-releasable.js "$PACKAGES_TO_CHECK_STR"
echo "packages_to_release=$PACKAGES_TO_CHECK_STR" >> "$GITHUB_OUTPUT"
prepare-release-branch:
runs-on: macos-latest
env:
GH_TOKEN: ${{ github.token }}
permissions:
contents: write
needs: validate-packages-as-releasable
outputs:
branch-name: ${{ steps.create-release-branch.outputs.branch_name }}
steps:
- name: Support long paths
run: git config --global core.longpaths true
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 'lts/*'
- name: Create release branch
id: create-release-branch
run: |
NOW_TIMESTAMP=$(date +%s)
git checkout -b release/$NOW_TIMESTAMP
# Immediately push the branch with no changes, so GraphQL can push to it later.
git push --set-upstream origin release/$NOW_TIMESTAMP
# Output the branch name so that it can be used later.
echo "branch_name=release/$NOW_TIMESTAMP" >> "$GITHUB_OUTPUT"
- name: Strip '-SNAPSHOT' from to-be-released package versions
run: |
PACKAGE_NAMES_STRING="${{ needs.validate-packages-as-releasable.outputs.packages-to-release }}"
node ./.github/workflows/publish-package-to-npm/update-versions-in-released-packages.js "$PACKAGE_NAMES_STRING"
- name: Update inter-package dependencies
run: |
PACKAGES_TO_RELEASE_STRING="${{ needs.validate-packages-as-releasable.outputs.packages-to-release }}"
cd packages
ALL_PACKAGES=`ls`
cd ..
node ./.github/workflows/publish-package-to-npm/update-dependencies-on-released-packages.js "$PACKAGES_TO_RELEASE_STRING" "$ALL_PACKAGES"
- name: Build
run: |
npm install
npm run build
# No need to test; that comes later.
- name: Commit changes to release branch
run: |
cd packages
ALL_PACKAGES=`ls`
cd ../.github/workflows/publish-package-to-npm
npm install
node commit-via-graphql.mjs "$ALL_PACKAGES"
build-and-test-and-publish:
runs-on: ubuntu-latest
needs: [validate-packages-as-releasable, prepare-release-branch]
steps:
- name: Support long paths
run: git config --global core.longpaths true
- uses: actions/checkout@v4
with:
ref: ${{ needs.prepare-release-branch.outputs.branch-name }}
- uses: actions/setup-node@v4
with:
node-version: 20
- name: Build and test and publish packages
run: |
PACKAGES_TO_PUBLISH=(${{ needs.validate-packages-as-releasable.outputs.packages-to-release }})
for PACKAGE_NAME in "${PACKAGES_TO_PUBLISH[@]}"
do
cd ./packages/${PACKAGE_NAME}
# Build and test each package individually instead of at the mono-repo level, to validate shared dependencies.
npm install
npm run build
npm run test
# We need the NPM token to publish.
echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > ~/.npmrc
PUBLISHED_VERSION=$(jq -r ".version" package.json)
if [[ "${{ inputs.dryrun }}" == "true" ]]; then
npm publish --tag latest-beta --access public --verbose --dry-run
echo "Fake-published ${PACKAGE_NAME}@${PUBLISHED_VERSION}"
else
npm publish --tag latest-beta --access public --verbose
echo "Published ${PACKAGE_NAME}@${PUBLISHED_VERSION}"
npm dist-tag add @salesforce/${PACKAGE_NAME}@${PUBLISHED_VERSION} latest
echo "Added latest tag to @salesforce/${PACKAGE_NAME}@${PUBLISHED_VERSION}"
fi
cd ../..
done
create-postrelease-pull-request:
runs-on: macos-latest
needs: [prepare-release-branch, build-and-test-and-publish]
if: ${{ inputs.dryrun == false }} # A Dry Run doesn't release, so no PR should be made
env:
GH_TOKEN: ${{ github.token }}
permissions:
contents: write
pull-requests: write
steps:
- name: Support long paths
run: git config --global core.longpaths true
- uses: actions/checkout@v4
with:
ref: ${{ needs.prepare-release-branch.outputs.branch-name }}
- run: |
echo -e "This branch and PR were automatically created as part of a Package Publish.\n\
The branch increments the .version property of published packages from X.Y.Z-SNAPSHOT to X.Y.Z, and updates any\
inter-package dependencies appropriately.\n\
The narrow scope of these changes makes a merge conflict unlikely, but if one does occur, you should consult\
with the author of the conflicting change and decide what to do next. Ultimately it may make sense to not merge\
this pull request at all. Use your judgment." > body.txt
gh pr create -B dev -H ${{ needs.prepare-release-branch.outputs.branch-name }} --title "POSTRELEASE @W-XXXXXXXX@ Merging after ecosystem release" -F body.txt