0.4.0 Package/deploy failure

[toddb]

The package is unable to be deployed to Nuget with the error:

Run dotnet nuget push /home/runner/work/novu-dotnet/novu-dotnet/output/Novu.0.4.0.nupkg -k *** -s https://api.nuget.org/v3/index.json
  dotnet nuget push /home/runner/work/novu-dotnet/novu-dotnet/output/Novu.0.4.0.nupkg -k *** -s https://api.nuget.org/v3/index.json
  shell: /usr/bin/bash -e {0}
  env:
    WORKING_DIRECTORY: ./src/
    PACKAGE_OUTPUT_DIRECTORY: /home/runner/work/novu-dotnet/novu-dotnet/output
    NUGET_SOURCE_URL: https://api.nuget.org/v3/index.json
    DOTNET_ROOT: /usr/share/dotnet
Pushing Novu.0.4.0.nupkg to 'https://www.nuget.org/api/v[2](https://github.com/novuhq/novu-dotnet/actions/runs/12753239583/job/35544462381#step:9:2)/package'...
  PUT https://www.nuget.org/api/v2/package/
  Forbidden https://www.nuget.org/api/v2/package/ [3](https://github.com/novuhq/novu-dotnet/actions/runs/12753239583/job/35544462381#step:9:3)89ms
error: Response status code does not indicate success: [4](https://github.com/novuhq/novu-dotnet/actions/runs/12753239583/job/35544462381#step:9:4)03 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).
Error: Process completed with exit code 1.

https://github.com/novuhq/novu-dotnet/actions/runs/12753239583/job/35544462381

@wh1337 @LetItRock @scopsy I am assuming that the keys need updating and I do not have rights to change settings.

[toddb]

The check secrets option refers to verifying that the secrets used in your GitHub Actions workflow are properly configured. Secrets are encrypted environment variables stored securely in your GitHub repository or organization. They allow you to securely pass sensitive information (like API tokens or passwords) to your workflow.

In your case, the secret NUGET_AUTH_TOKEN is used to authenticate with NuGet when pushing packages. Here's how you can verify and manage your secrets:

---

Steps to Check Secrets in GitHub

1. Navigate to Secrets Settings

   • Go to your GitHub repository.
   • Click on Settings in the repository menu.
   • Scroll down to Secrets and variables under the Security section.
   • Select Actions.

2. Verify the Secret Exists

   • Look for NUGET_AUTH_TOKEN in the list of secrets.
   • If it doesn’t exist, create it:
     • Click New repository secret.
     • Enter NUGET_AUTH_TOKEN as the name.
     • Paste the authentication token for NuGet into the value field.
     • Click Add secret.

3. Ensure the Secret is Correct

   • The value of NUGET_AUTH_TOKEN should be a valid API key for your NuGet account.
   • You can generate a NuGet API key:
     • Go to the [NuGet.org API Keys page](https://www.nuget.org/account/apikeys).
     • Click Create, set the scope to Push, and choose the expiration and project constraints.
     • Copy the API key and save it as the NUGET_AUTH_TOKEN secret in GitHub.

4. Check Workflow Permissions

   • In the Settings > Actions > General section of your repository, ensure the workflow permissions are correctly configured:
     • Read and write permissions: The workflow requires write permissions to access secrets.
     • Enable Allow GitHub Actions to create and approve pull requests if needed for pushing changes.

5. Log Secrets Usage

   • To verify that the secret is accessible, you can log a placeholder (never log the actual secret):

     - run: echo "NuGet Auth Token Length: ${#secrets.NUGET_AUTH_TOKEN}"

---

Common Issues with Secrets

1. Missing or Incorrect Secret

   • If the secret is not set or has an incorrect value, the workflow will fail with an authentication error.

2. Repository Access

   • Secrets are scoped to the repository or organization where they are defined. Ensure your workflow runs in a repository that has access to the secret.

3. Token Expiration

   • If the NuGet API key has expired, you'll need to generate a new one and update the secret in GitHub.

---

Example Usage in Workflow

Here’s how you’re using the NUGET_AUTH_TOKEN secret in your workflow:

run: dotnet nuget push ${{ env.PACKAGE_OUTPUT_DIRECTORY}}/Novu.${{ steps.version.outputs.version-without-v }}.nupkg -k ${{ secrets.NUGET_AUTH_TOKEN }} -s ${{ env.NUGET_SOURCE_URL}}

• ${{ secrets.NUGET_AUTH_TOKEN }}: Injects the secret securely into the workflow.
• NuGet Authentication: This token authorizes the dotnet nuget push command to upload packages.

By following these steps and ensuring the NUGET_AUTH_TOKEN is valid, you should resolve any issues related to secrets. Let me know if you encounter specific errors!