feat: add Huawei and email_reply_to_address parameters to Notification#80
feat: add Huawei and email_reply_to_address parameters to Notification#80sherwinski merged 1 commit intomainfrom
Conversation
8d3a5fb to
826f752
Compare
826f752 to
656172a
Compare
656172a to
525cf20
Compare
525cf20 to
4e17b36
Compare
| name: Publish to NuGet | ||
| needs: release | ||
| if: needs.release.outputs.new_release_published == 'true' | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v5 | ||
| - name: Setup dotnet | ||
| uses: actions/setup-dotnet@v5 | ||
| with: | ||
| dotnet-version: 8.x | ||
| - name: Build and Pack | ||
| run: | | ||
| dotnet restore | ||
| dotnet build --configuration Release --no-restore | ||
| dotnet pack src/OneSignalApi/OneSignalApi.csproj --configuration Release --no-build --output nupkgs | ||
| - name: Publish to NuGet | ||
| run: dotnet nuget push nupkgs/*.nupkg --api-key ${{ secrets.NUGET_API_KEY }} --source https://api.nuget.org/v3/index.json |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 days ago
In general, the fix is to add an explicit permissions block either at the workflow root (applying to all jobs) or specifically on jobs that currently rely on default GITHUB_TOKEN permissions. Here, the release job already has a correctly scoped permissions block; only the publish job is missing one.
The best targeted fix without changing functionality is to add a permissions block to the publish job that grants only contents: read. This is sufficient, since publish needs only to check out code and then interact with NuGet using secrets.NUGET_API_KEY, not modify anything in the GitHub repository. Concretely, in .github/workflows/release.yml, under jobs:, inside the publish: job definition (around line 45), insert:
permissions:
contents: readright after runs-on: ubuntu-latest (or equivalently near the top of the job’s keys). No imports or additional methods are required, as this is purely a YAML configuration change in the workflow file.
| @@ -46,6 +46,8 @@ | ||
| needs: release | ||
| if: needs.release.outputs.new_release_published == 'true' | ||
| runs-on: ubuntu-latest | ||
| permissions: | ||
| contents: read | ||
| steps: | ||
| - uses: actions/checkout@v5 | ||
| - name: Setup dotnet |
email_reply_to_address parameters to Notification
email_reply_to_address parameters to Notification39e1526 to
862db62
Compare
## [5.4.0](v5.3.0...v5.4.0) (2026-03-24) ### Features * add Huawei and email_reply_to_address parameters to Notification ([#80](#80)) ([205cefb](205cefb)) [skip ci]
|
🎉 This PR is included in version 5.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Features
Adds the following
Notificationparameters:huawei_badge_classhuawei_badge_add_numhuawei_badge_set_numhuawei_categoryhuawei_bi_tagemail_reply_to_address