connect dwn integration (#850) #259
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: release snapshot to jfrog | |
on: | |
push: | |
branches: | |
- main | |
workflow_dispatch: | |
# Allow only one concurrent deployment, but do NOT cancel in-progress runs as | |
# we want to allow these release deployments to complete. | |
concurrency: | |
group: ${{ github.workflow }}-${{ github.ref }} | |
cancel-in-progress: false | |
permissions: | |
contents: read | |
id-token: write | |
jobs: | |
publish-npm: | |
name: Snapshot Publish | |
runs-on: ubuntu-latest | |
strategy: | |
matrix: | |
package: | |
[ | |
"agent", | |
"api", | |
"common", | |
"credentials", | |
"crypto", | |
"crypto-aws-kms", | |
"dids", | |
"identity-agent", | |
"proxy-agent", | |
"user-agent", | |
] | |
steps: | |
- name: Checkout source | |
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 #v4.1.1 | |
with: | |
fetch-depth: 0 | |
# https://cashapp.github.io/hermit/usage/ci/ | |
- name: Init Hermit | |
uses: cashapp/activate-hermit@31ce88b17a84941bb1b782f1b7b317856addf286 #v1.1.0 | |
with: | |
cache: "true" | |
- uses: jfrog/setup-jfrog-cli@d82fe26823e1f25529250895d5673f65b02af085 #v4.0.1 | |
with: | |
version: latest | |
oidc-provider-name: github # must match the OpenID Connect name from https://blockxyz.jfrog.io/ui/admin/configuration/integrations | |
env: | |
JF_URL: https://blockxyz.jfrog.io | |
- name: Publish @web5/${{ matrix.package }} snapshot | |
env: | |
NODE_AUTH_TOKEN: ${{secrets.npm_token}} | |
REGISTRY: https://blockxyz.jfrog.io/artifactory/api/npm/tbd-oss-snapshots-npm/ | |
run: | | |
set -exuo pipefail | |
package_name="${{ matrix.package }}" | |
cd "packages/${package_name}" | |
base_version=$(jq -r .version package.json) | |
# I'm not seeing a great way to determine the commit of the last release of a given package, so I'm using a not-so-great way | |
version_line=$(grep -n "\"version\": \"${base_version}\"" package.json | cut -d: -f1) # determine which line in package.json specifies the version | |
version_bump_commit=$(git blame --porcelain -L "${version_line},${version_line}" -- package.json | head -n1 | awk '{ print $1 }') # ask git when the last commit to that line was | |
commits_since_version_bump=$(git rev-list HEAD ${version_bump_commit} --count -- .) # count the number of commits that changed this package since the version change commit | |
last_commit_to_package="$(git log -1 --pretty=format:%H -- .)" | |
snapshot_version="${base_version}-SNAPSHOT.${commits_since_version_bump}-${last_commit_to_package:0:7}" | |
# check if that snapshot version has already been published | |
if npm view --registry "${REGISTRY}" "@web5/${package_name}@${snapshot_version}" > /dev/null; then | |
echo "release for @web5/${package_name}-${snapshot_version} already exists, not re-publishing" | |
exit 0 | |
fi | |
pushd ../.. | |
pnpm install | |
pnpm build | |
popd | |
# set the snapshot version | |
jq --arg version "${snapshot_version}" '.version = $version' package.json > package-new.json | |
mv package-new.json package.json | |
# set publishing config in package.json | |
jq --arg registry "${REGISTRY}" '.publishConfig.registry = $registry' package.json > package-new.json | |
mv package-new.json package.json | |
# login to jfrog and publish | |
jf npm-config --global=true --repo-resolve=tbd-oss-snapshots-npm --repo-deploy=tbd-oss-snapshots-npm | |
jf npm publish --registry "${REGISTRY}" | |
shell: bash |