Release from a tag: CI builds and publishes, with one tag style across the three libraries
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #212 来自 @jasperblues —— 已合并
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
调研方向
Start by reading pyproject.toml for the project version and build configuration, then inspect the repository’s existing GitHub Actions workflows and release process. Implement and document the tag-triggered release flow described in the issue, including the version check, wheel smoke test, and trusted publishing setup. Done means a test tag completes the dry run, RELEASING.md is merged, and the required secrets or publisher configuration are documented for the maintainer.
由索引模型根据 Issue 内容生成。
描述
The 0.3.0 / 3.3.0 / 0.2.0 releases were built and tagged by hand, and they drifted. drivine4j was published from main past its release PR, so its tag had to follow what was published. drivine nearly went out from a checkout with a stale node_modules. The tag styles also differ (0.3.0 in drivine4j, vX.Y.Z in the others).
The same release process for all three libraries:
- A release PR bumps the version and the changelog. It is reviewed and passes CI like any other PR.
- Merging it is the release point. The merge commit is tagged
vX.Y.Z, the same style in all three repos. - A tag push runs a GitHub Actions workflow that checks out the tag, runs the full gate, builds, and publishes. Nothing is built from a local checkout.
- Credentials live as repo secrets (or trusted publishing), never on a laptop.
RELEASING.mddescribes the steps. Each repo has the same file, differing only in its publish step.
Done when:
- a dry run (to a staging target or with publish skipped) works from a test tag;
RELEASING.mdis merged;- the secrets are listed for the maintainer to add.
Use it for the next release, once the "Next release + 1" backlog is cleared.
drivine-python specifics:
- Publish:
uv build(hatchling), then upload to PyPI with trusted publishing (OIDC); no token needed. - Setup: configure a PyPI trusted publisher for the repo and workflow.
- Check:
pyproject.toml's version matches the tag, or the job fails. - Smoke test: after the build, install the wheel into a clean venv and run
python -m drivine.stubs.
- 主要语言
- Python
- 星标
- 1
- 派生
- 0
- 平均合并
- 1 小时 29 分钟
- 30 天内合并 PR
- 136
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
liberation-data/drivine-python 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
liberation-data/drivine-python#250 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
liberation-data/drivine-python#209 ·
维护者通常 1 天内回复
-
CI: three Oracle-only tests in test_cypher_compiled.py never run, as -k oracle doesn't select them未关闭
难度 1/5 1 小时以内 新手友好度 88/100
liberation-data/drivine-python#178 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 55/100
liberation-data/drivine-python#297 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
liberation-data/drivine-python#295 ·
维护者通常 1 天内回复
查看 liberation-data/drivine-python 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
BCDA-APS/polar-bits#93 ·
-
infer_audio_type only recognises one MPEG Layer III frame header, so most MP3 files are rejected可能已有人在做 @Steve-20-ai 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[BUG] - ssh_config `Match tagged` statement always applies可能已有人在做 @AtharvRG 今天认领。 未关闭Bug
难度 2/5 1-3 小时 新手友好度 68/100
paramiko/paramiko#2715 · 1 条评论 ·
维护者通常 9 天内回复
-
auto-rejected intake mcp-intake needs-salvage priority:high type:feature
难度 2/5 1-3 小时 新手友好度 65/100
Ikalus1988/MisakaNet#4221 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复