semantic-release 17.3.8 → 17.3.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
<h1 align="center" style="border-bottom: none;">📦🚀 semantic-release</h1>
|
|
2
2
|
<h3 align="center">Fully automated version management and package publishing</h3>
|
|
3
3
|
<p align="center">
|
|
4
|
-
<a href="https://
|
|
5
|
-
<img alt="Join the community on
|
|
4
|
+
<a href="https://github.com/semantic-release/semantic-release/discussions">
|
|
5
|
+
<img alt="Join the community on GitHub Discussions" src="https://img.shields.io/badge/Join%20the%20community-on%20GitHub%20Discussions-blue">
|
|
6
6
|
</a>
|
|
7
7
|
<a href="https://github.com/semantic-release/semantic-release/actions?query=workflow%3ATest+branch%3Amaster">
|
|
8
8
|
<img alt="Build states" src="https://github.com/semantic-release/semantic-release/workflows/Test/badge.svg">
|
|
@@ -131,7 +131,7 @@ In order to use **semantic-release** you need:
|
|
|
131
131
|
## Get help
|
|
132
132
|
|
|
133
133
|
- [Stack Overflow](https://stackoverflow.com/questions/tagged/semantic-release)
|
|
134
|
-
- [
|
|
134
|
+
- [GitHub Discussions](https://github.com/semantic-release/semantic-release/discussions)
|
|
135
135
|
- [Twitter](https://twitter.com/SemanticRelease)
|
|
136
136
|
|
|
137
137
|
## Badge
|
|
@@ -91,6 +91,9 @@
|
|
|
91
91
|
- [semantic-release-github-pages](https://github.com/qiwi/semantic-release-gh-pages-plugin)
|
|
92
92
|
- `verifyConditions`: Verify the presence of the auth token set via environment variables.
|
|
93
93
|
- `publish`: Pushes commit to the documentation branch.
|
|
94
|
+
- [semantic-release-github-pullrequest](https://github.com/asbiin/semantic-release-github-pullrequest)
|
|
95
|
+
- `verifyConditions`: Verify the presence and the validity of the GitHub authentication and other configuration.
|
|
96
|
+
- `publish`: Create a branch to upload all assets and create the pull request on the base branch on GitHub.
|
|
94
97
|
- [leiningen-semantic-release](https://github.com/NoxHarmonium/leiningen-semantic-release)
|
|
95
98
|
- `verifyConditions`: Checks the project.clj is syntactically valid.
|
|
96
99
|
- `prepare`: Update the project.clj version and package the output jar file.
|
|
@@ -8,7 +8,7 @@ Here is a few example of the CI services that can be used to achieve this:
|
|
|
8
8
|
- [CircleCI Workflows](https://circleci.com/docs/2.0/workflows)
|
|
9
9
|
- [GitHub Actions](https://github.com/features/actions)
|
|
10
10
|
- [Codeship Deployment Pipelines](https://documentation.codeship.com/basic/builds-and-configuration/deployment-pipelines)
|
|
11
|
-
- [GitLab Pipelines](https://docs.gitlab.com/
|
|
11
|
+
- [GitLab Pipelines](https://docs.gitlab.com/ce/ci/introduction/)
|
|
12
12
|
- [Codefresh Pipelines](https://codefresh.io/docs/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines)
|
|
13
13
|
- [Wercker Workflows](http://devcenter.wercker.com/docs/workflows)
|
|
14
14
|
- [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline).
|
package/package.json
CHANGED