You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/ScriptModuleRepositoryTemplate/TemplateRepoFiles/ReadMe.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,6 +67,14 @@ If using GitHub Actions for your CI/CD workflows, perform the following steps to
67
67
1. Set the `Name` to: `POWERSHELL_GALLERY_API_KEY`
68
68
1. Set the `Secret` to the API key value that you copied in the previous section.
69
69
70
+
If you do not provide a valid API key, you will get an error like the following in the `Publish prerelease PowerShell module` step of the deployment workflow:
71
+
72
+
```text
73
+
Failed to publish module '<module name>': 'dotnet cli failed to nuget push Pushing <module name>.nupkg to '<url>'...
74
+
PUT <url> Forbidden
75
+
error: Response status code does not indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).
76
+
```
77
+
70
78
Next we want to create an Environment so that stable module versions require manual approval before being published to the gallery:
71
79
72
80
1. You should still be in the `Settings` section of your repository.
0 commit comments