chore: Configure Renovate (#16)
Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
Detected Package Files
.github/workflows/node-release-no-provenance.yml(github-actions).github/workflows/node-release.yml(github-actions).github/workflows/node-test-mysql.yml(github-actions).github/workflows/node-test-parallel.yml(github-actions).github/workflows/node-test.yml(github-actions).github/workflows/npm-release.yml(github-actions)scripts/npm-release/package.json(npm)scripts/release/package.json(npm)Configuration Summary
Based on the default config’s presets, Renovate will:
- Start dependency updates only once this onboarding PR is merged
- Hopefully safe environment variables to allow users to configure.
- Show all Merge Confidence badges for pull requests.
- Enable Renovate Dependency Dashboard creation.
- Use semantic commit type
fixfor dependencies andchorefor all others if semantic commits are in use.- Ignore
node_modules,bower_components,vendorand various test/tests (except for nuget) directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Show only the Age and Confidence Merge Confidence badges for pull requests.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
- Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
- Correctly link to the source code for golang.org/x packages
- Link to pkg.go.dev/… for golang.org/x packages’ title
🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to
renovate.jsonin this branch. Renovate will update the Pull Request description the next time it runs.
What to Expect
With your current configuration, Renovate will create 12 Pull Requests:
fix(deps): update semantic-release monorepo
- Schedule: [“at any time”]
- Branch name:
renovate/semantic-release-monorepo- Merge into:
master- Upgrade @semantic-release/npm to
13.1.3- Upgrade semantic-release to
25.0.2chore(deps): update actions/checkout action to v6
- Schedule: [“at any time”]
- Branch name:
renovate/actions-checkout-6.x- Merge into:
master- Upgrade actions/checkout to
v6chore(deps): update actions/github-script action to v8
- Schedule: [“at any time”]
- Branch name:
renovate/actions-github-script-8.x- Merge into:
master- Upgrade actions/github-script to
v8chore(deps): update actions/setup-node action to v6
- Schedule: [“at any time”]
- Branch name:
renovate/actions-setup-node-6.x- Merge into:
master- Upgrade actions/setup-node to
v6chore(deps): update codecov/codecov-action action to v5
- Schedule: [“at any time”]
- Branch name:
renovate/codecov-codecov-action-5.x- Merge into:
master- Upgrade codecov/codecov-action to
v5chore(deps): update dependency @types/node to v24
- Schedule: [“at any time”]
- Branch name:
renovate/node-24.x- Merge into:
master- Upgrade @types/node to
^24.0.0chore(deps): update dependency @types/semantic-release to v21
- Schedule: [“at any time”]
- Branch name:
renovate/semantic-release-21.x- Merge into:
master- Upgrade @types/semantic-release to
^21.0.0fix(deps): update dependency @actions/core to v2
- Schedule: [“at any time”]
- Branch name:
renovate/actions-core-2.x- Merge into:
master- Upgrade @actions/core to
^2.0.0fix(deps): update dependency @actions/exec to v2
- Schedule: [“at any time”]
- Branch name:
renovate/actions-exec-2.x- Merge into:
master- Upgrade @actions/exec to
^2.0.0fix(deps): update dependency conventional-changelog-conventionalcommits to v9
- Schedule: [“at any time”]
- Branch name:
renovate/conventional-changelog-conventionalcommits-9.x
- Merge into:
master- Upgrade conventional-changelog-conventionalcommits to
^9.0.0fix(deps): update dependency undici to v7
- Schedule: [“at any time”]
- Branch name:
renovate/undici-7.x- Merge into:
master- Upgrade undici to
^7.0.0fix(deps): update semantic-release monorepo (major)
- Schedule: [“at any time”]
- Branch name:
renovate/major-semantic-release-monorepo- Merge into:
master- Upgrade @semantic-release/exec to
^7.0.0- Upgrade @semantic-release/github to
^12.0.0- Upgrade semantic-release to
^25.0.0🚸 Branch creation will be limited to maximum 2 per hour, so it doesn’t swamp any CI resources or overwhelm the project. See docs for
prhourlylimitfor details.
❓ Got questions? Check out Renovate’s Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.
This PR was generated by Mend Renovate. View the repository job log.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802032778号
node-modules/github-actions
为开源项目提供常见的可复用的 GitHub Actions Workflow。
功能列表
单元测试
自动跑 Lint 和 Cov 单测
npm scripts:.github/workflows/ci.yml:开启 MySQL 和 Redis 服务依赖
开启并行测试
发布 NPM 包
使用 semantic-release 自动发布 NPM 包。
功能详情
支持合并到主干分支后自动发布,也支持手动发布。
版本号规则
根据 Commit Message 自动计算下一个版本号:
BREAKING CHANGE:,必须加到 commit body 里面而不是第一行标题,否则不生效feat:等fix:/Revert等chore:/docs:/style:等注意:
beta分支提交代码运行,将发布1.0.0-beta.1版本配置方式
创建 GitHub Token
GITHUB_TOKEN没有该权限。如会被保护分支规则拦截。配置 Token
GIT_TOKEN创建
.github/workflows/release.yml:发布到 GitHub Package
修改
package.json: