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
)}) if defined, must be an \`Array\` of non empty \`String\`.
58
77
59
78
Your configuration for the \`releasedLabels\` option is \`${stringify(releasedLabels)}\`.`,
60
-
}),
61
-
EINVALIDADDRELEASES: ({addReleases})=>({
79
+
};
80
+
}
81
+
82
+
exportfunctionEINVALIDADDRELEASES({addReleases}){
83
+
return{
62
84
message: 'Invalid `addReleases` option.',
63
85
details: `The [addReleases option](${linkify('README.md#options')}) if defined, must be one of \`false|top|bottom\`.
64
86
65
87
Your configuration for the \`addReleases\` option is \`${stringify(addReleases)}\`.`,
66
-
}),
67
-
EINVALIDGITHUBURL: ()=>({
88
+
};
89
+
}
90
+
91
+
exportfunctionEINVALIDGITHUBURL(){
92
+
return{
68
93
message: 'The git repository URL is not a valid GitHub URL.',
69
94
details: `The **semantic-release** \`repositoryUrl\` option must a valid GitHub URL with the format \`<GitHub_or_GHE_URL>/<owner>/<repo>.git\`.
70
95
71
96
By default the \`repositoryUrl\` option is retrieved from the \`repository\` property of your \`package.json\` or the [git origin url](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) of the repository cloned by your CI environment.`,
72
-
}),
73
-
EINVALIDPROXY: ({proxy})=>({
97
+
};
98
+
}
99
+
100
+
exportfunctionEINVALIDPROXY({proxy}){
101
+
return{
74
102
message: 'Invalid `proxy` option.',
75
103
details: `The [proxy option](${linkify(
76
104
'README.md#proxy'
77
105
)}) must be a \`String\` or an \`Objects\` with a \`host\` and a \`port\` property.
78
106
79
107
Your configuration for the \`proxy\` option is \`${stringify(proxy)}\`.`,
details: `The **semantic-release** \`repositoryUrl\` option must refer to your GitHub repository. The repository must be accessible with the [GitHub API](https://developer.github.com/v3).
84
115
@@ -87,29 +118,38 @@ By default the \`repositoryUrl\` option is retrieved from the \`repository\` pro
87
118
If you are using [GitHub Enterprise](https://enterprise.github.com) please make sure to configure the \`githubUrl\` and \`githubApiPathPrefix\` [options](${linkify(
88
119
'README.md#options'
89
120
)}).`,
90
-
}),
91
-
EGHNOPERMISSION: ({owner, repo})=>({
121
+
};
122
+
}
123
+
124
+
exportfunctionEGHNOPERMISSION({owner, repo}){
125
+
return{
92
126
message: `The GitHub token doesn't allow to push on the repository ${owner}/${repo}.`,
93
127
details: `The user associated with the [GitHub token](${linkify(
94
128
'README.md#github-authentication'
95
129
)}) configured in the \`GH_TOKEN\` or \`GITHUB_TOKEN\` environment variable must allows to push to the repository ${owner}/${repo}.
96
130
97
131
Please make sure the GitHub user associated with the token is an [owner](https://help.github.com/articles/permission-levels-for-a-user-account-repository/#owner-access-on-a-repository-owned-by-a-user-account) or a [collaborator](https://help.github.com/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account) if the reposotory belong to a user account or has [write permissions](https://help.github.com/articles/managing-team-access-to-an-organization-repository) if the repository [belongs to an organization](https://help.github.com/articles/repository-permission-levels-for-an-organization).`,
98
-
}),
99
-
EINVALIDGHTOKEN: ({owner, repo})=>({
132
+
};
133
+
}
134
+
135
+
exportfunctionEINVALIDGHTOKEN({owner, repo}){
136
+
return{
100
137
message: 'Invalid GitHub token.',
101
138
details: `The [GitHub token](${linkify(
102
139
'README.md#github-authentication'
103
140
)}) configured in the \`GH_TOKEN\` or \`GITHUB_TOKEN\` environment variable must be a valid [personal token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) allowing to push to the repository ${owner}/${repo}.
104
141
105
142
Please make sure to set the \`GH_TOKEN\` or \`GITHUB_TOKEN\` environment variable in your CI with the exact value of the GitHub personal token.`,
106
-
}),
107
-
ENOGHTOKEN: ({owner, repo})=>({
143
+
};
144
+
}
145
+
146
+
exportfunctionENOGHTOKEN({owner, repo}){
147
+
return{
108
148
message: 'No GitHub token specified.',
109
149
details: `A [GitHub personal token](${linkify(
110
150
'README.md#github-authentication'
111
151
)}) must be created and set in the \`GH_TOKEN\` or \`GITHUB_TOKEN\` environment variable on your CI environment.
112
152
113
153
Please make sure to create a [GitHub personal token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) and to set it in the \`GH_TOKEN\` or \`GITHUB_TOKEN\` environment variable on your CI environment. The token must allow to push to the repository ${owner}/${repo}.`,
0 commit comments