No description
- Python 99%
- Makefile 1%
renovate-bot
cfbd32957a
Welcome to [Renovate](https://github.com/renovatebot/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. 📚 See our [Reading List](https://docs.renovatebot.com/reading-list/) for relevant documentation you may be interested in reading. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs. --- ### Detected Package Files * `pyproject.toml` (pep621) * `.python-version` (pyenv) * `renovate.json` (renovate-config) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and 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 Forgejo contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitLab.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 - Pin Docker digests. - Pin `github-action` digests. - Enable Renovate configuration migration PRs when needed. - Pin dependency versions for development dependencies. - Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides. - Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds. - Run lock file maintenance (updates) early Monday mornings. - Disable Renovate Dependency Dashboard creation. - default base preset for Forgejo repos --- ### What to Expect With your current configuration, Renovate will create 2 Pull Requests: <details> <summary>chore(deps): update python docker tag to v3.14</summary> - Schedule: ["at any time"] - Branch name: `renovate/python-3.x` - Merge into: `main` - Upgrade python to `3.14` </details> <details> <summary>chore(deps): lock file maintenance</summary> - Schedule: ["* 0-3 * * 1"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:87ef954a3c283e5ea88f5d2b3074b9d332f4100e00a9a1a20db57c6a63a95ac3--> Reviewed-on: #1 |
||
|---|---|---|
| data | ||
| src/manager | ||
| .editorconfig | ||
| .env.example | ||
| .gitignore | ||
| .python-version | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| renovate.json | ||
| ruff.toml | ||
| uv.lock | ||
ckb-next-helper
Prereqs
- Python 3.13 or newer
gh(GitHub CLI)- A local checkout of ckb-next.wiki
Getting started
With uv
uv sync
manager info 1b98
Without uv
Create a virtualenv and install the project into it:
python3.13 -m venv .venv
source .venv/bin/activate
pip install -e .
# local only command
manager info 1b98
Configuration
manager wiki-export reads CKB_NEXT_WIKI from .env:
cp .env.example .env
# edit .env and set CKB_NEXT_WIKI=/path/to/ckb-next.wiki
Usage
manager issue 1261
manager report https://github.com/user-attachments/files/25269935/ckb-next-dev-detect-report.gz
manager wiki-export
manager add-requested 1261
manager info 1b98
manager edit 1b98
Issue JSON and the downloaded .gz attachment are cached under
.cache/<issue>/ in the project root. Pass --overwrite to bypass the cache.