(fix) add entries as a valid export (#2001) #136
Workflow file for this run
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: Tagged Production Deploys for VS Code | |
on: | |
push: | |
tags: | |
- "extensions-*" | |
jobs: | |
deploy: | |
runs-on: ubuntu-latest | |
steps: | |
- uses: actions/checkout@v3 | |
- uses: actions/setup-node@v3 | |
with: | |
node-version: "16.x" | |
registry-url: "https://registry.npmjs.org" | |
cache: yarn | |
# Ensure everything is compiling | |
- run: "yarn install" | |
- run: "yarn build" | |
- run: "yarn bootstrap" | |
# Lets us use one-liner JSON manipulations the package.json files | |
- run: "npm install -g json" | |
# Setup the environment | |
- run: 'json -I -f packages/svelte-vscode/package.json -e "this.version=\`${{ github.ref }}\`.split(\`-\`).pop()"' | |
# To deploy we need isolated node_modules folders which yarn won't do because it is a workspace | |
# So, remove the workspace | |
- run: "rm package.json yarn.lock" # Re-run the yarn install outside of the workspace | |
- run: | | |
cd packages/svelte-vscode | |
yarn install | |
# Just a hard constraint from the vscode marketplace's usage of azure tokens | |
echo "Once a year this expires, tell Orta to access https://dev.azure.com/ortatherox0608/_usersSettings/tokens (logging in with GitHub) to get a new one" | |
# Ship it | |
npx vsce publish --yarn -p $VSCE_TOKEN | |
npx ovsx publish --yarn -p $OVSX_TOKEN | |
env: | |
VSCE_TOKEN: ${{ secrets.AZURE_PAN_TOKEN }} | |
OVSX_TOKEN: ${{ secrets.OVSX_TOKEN }} |