File tree Expand file tree Collapse file tree 1 file changed +10
-0
lines changed Expand file tree Collapse file tree 1 file changed +10
-0
lines changed Original file line number Diff line number Diff line change @@ -16,6 +16,16 @@ After the action finishes successfully you have to manually release the Go packa
1616The release version is determinated based on the [ Conventional Commits] ( https://www.conventionalcommits.org/en/v1.0.0/#summary ) in that release.
1717
1818
19+ ## Release troubleshooting
20+ If the Release Gitub Action fails, it can happen that the new version is published only to some repositories,
21+ but the failing ones are still in the current version.
22+
23+ The current version is only updated when the Github Action is completely succesful. Also the action is retryable
24+ (all repository publishings are idempotent, if try to publish a version that is already published, it doesn't fail and behaves like a no-op).
25+ ** That means that the offending issue can be fixed and run the action again.**
26+
27+ You can also do a manual release for the failing repository publishings.
28+
1929## Manual Release
2030
2131** Note, we should manual release a version only if one of the Publish step of the action failed.**
You can’t perform that action at this time.
0 commit comments