b5edaeb950
This PR sets up our publish-new script to use Huppy's GH token. At the same time I added huppy to a list of actors who are allowed to override the branch protection rules for `main` so hopefully next time we run the release script the push will succeed and the release will therefore also succeed. I will create a test repo to see if that works and if it does I'll merge this. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version
36 lines
1,014 B
YAML
36 lines
1,014 B
YAML
name: (Re)Publish public packages manually
|
|
# This only attempts to publish the public packages to npm.
|
|
# It does not bump the version, it does not update the changelogs, it does not create a github release.
|
|
|
|
# Package publishing is manually triggered on github actions dashboard
|
|
on: workflow_dispatch
|
|
|
|
jobs:
|
|
deploy:
|
|
name: '(Re)Publish public packages manually'
|
|
environment: npm deploy
|
|
timeout-minutes: 15
|
|
runs-on: ubuntu-latest-16-cores-open
|
|
|
|
steps:
|
|
- name: Check out code
|
|
uses: actions/checkout@v3
|
|
|
|
- name: Setup Node.js environment
|
|
uses: actions/setup-node@v3
|
|
with:
|
|
node-version: 18
|
|
cache: 'yarn'
|
|
cache-dependency-path: 'public-yarn.lock'
|
|
|
|
- name: Enable corepack
|
|
run: corepack enable
|
|
|
|
- name: Install dependencies
|
|
run: yarn
|
|
|
|
- name: Publish
|
|
run: yarn tsx ./scripts/publish-manual.ts
|
|
env:
|
|
GH_TOKEN: ${{ github.token }}
|
|
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
|