Skip to content

types/capability: allow wildcard capability when presented in object form, add privileged-headers capability #2478

types/capability: allow wildcard capability when presented in object form, add privileged-headers capability

types/capability: allow wildcard capability when presented in object form, add privileged-headers capability #2478

Workflow file for this run

name: Bundle size report
on:
pull_request:
push:
branches:
- main
jobs:
bundle-report:
runs-on: ubuntu-latest
permissions:
deployments: write
id-token: write
steps:
- uses: actions/checkout@v2
- name: Reconfigure git to use HTTP authentication
run: >
git config --global url."https://github.com/".insteadOf
ssh://[email protected]/
- name: Use Node.js 20.x
uses: actions/setup-node@v1
with:
node-version: 20.x
- run: npm ci
- name: Build bundle reports
run: |
mkdir bundle-reports
npm run sourcemap -- --html bundle-reports/index.html
- uses: aws-actions/configure-aws-credentials@v1
with:
aws-region: eu-west-2
role-to-assume: arn:aws:iam::${{ secrets.ABLY_AWS_ACCOUNT_ID_SDK }}:role/ably-sdk-builds-ably-js
role-session-name: "${{ github.run_id }}-${{ github.run_number }}"
- uses: ably/sdk-upload-action@v1
with:
sourcePath: bundle-reports
githubToken: ${{ secrets.GITHUB_TOKEN }}
artifactName: bundle-report
# This step performs some validation and may fail, so it should come after the steps that we want to always execute.
- run: npm run modulereport