aevea/release-notary!Test !GitHub release (latest by date) !GitHub commits since latest release
Release Notary builds release notes using Conventional Commit standard and then publishes it to Github. Release notes are appended to any text you already have in your release and therefore will not affect important announcements etc.
Currently supported providers are: [Github, Gitlab].
Heavily inspired by [***] but usable as a standalone app.
Expected output is HERE
:warning: Currently experimental. Please report any issues :warning:
Variables:
| Name | Example value | Required |
|---|---|---|
| GITHUB_TOKEN | token (provided in Github Action or HERE) | true |
| GITHUB_REPOSITORY | commitsar-app/commitsar | true |
In Github actions GITHUB_REPOSITORY is provided in the correct format. Does not need to be explicitly added.
In Github actions GITHUB_TOKEN is provided with the correct access rights, elsewhere it needs to be generated and added to the pipeline. Please see the usage section.
Variables:
In Gitlab CI all the values are provided except for GITLAB_TOKEN. Documentation provided here.
| Name | Example value | Required |
|---|---|---|
| GITLAB_TOKEN | token | true |
| CI_API_V4_URL | [***] | true |
| CI_COMMIT_TAG | v0.0.4 | true |
| CI_PROJECT_ID | 1234 | true |
Slack integration posts release notes into Slack using the Incoming webhook integration. Slack Documentation
| Name | Example value | Required |
|---|---|---|
| SLACK_WEBHOOK | [***] | false |
actions/checkout@v2
actions/checkout@v2 behaves differently from the first version. It pulls in just the latest commit and does not pull any other git objects. Release Notary needs these objects in order to work.
It should be run only on tags.
Example workflow file:
yamlname: Release on: push: tags: - v* jobs: release-notes: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v2 with: fetch-depth: 0 - name: Release Notary Action uses: docker://aevea/release-notary:0.9.1 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
actions/checkout@v1
Should be run only on tags, example is HERE:
ymlon: push: tags: - "v*"
Checkout git in order to get commits and master branch
yml- name: Check out code into the Go module directory uses: actions/checkout@v1
Run the Release Notary action. Github token needs to be explicitly added so that Release Notary can use it. See [***]
yml- name: Release Notary Action uses: aevea/release-notary@v0.2.0 (substitute for current version) env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
ymlrelease: stage: release variables: GITLAB_TOKEN: $RELEASE_TOKEN image: name: aevea/release-notary:latest entrypoint: [""] script: - release-notary publish only: - tags
Download and run: (Substitute v0.0.2 for current version)
yml- curl -L -O [***] - tar -xzf release-notary_v0.0.2_Linux_x86_64.tar.gz # Set up any required variables - export GITHUB_TOKEN=yourtoken - export GITHUB_REPOSITORY=owner/repo - ./release-notary publish
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务