AUTO-MAS MaaFW Project Update
MFW 插件族的「项目更新」服务插件(插件标识 maafw_project_update)。负责:
- 项目副本:载荷库(
data/maafw_blobs、data/mfw/.payloads)与各托管的视图(data/mfw/<视图>); - 导入、重导、克隆、立即同步,以及手动 / 运行前后的项目更新与预下载;
- 启动期维护(旧副本迁移、属主标记、副本 / agent 环境 / 运行池 / 更新缓存清理)和每日原生日志清理;
/api/scripts/maafw/*下的 13 个端点(外壳配置导入的 3 个归maafw_adapter);- 托管属主登记:三个专项各自提供属主服务
maafw.owner.<专项>.v1,在本插件登记。
三个专项共用的配置胶水(默认任务快照、选项密码、账号更新准备、备份归档、属主入口)0.1.0 放在本包
glue/ 下,之后搬进了库 auto-mas-maafw-adapter-kit(maafw_adapter_kit)。
对外服务:maafw.project.v1 与 maafw.project_update.v1,都指向同一个分发方法
call(op, /, **kwargs)。0.1.0 实现的 op:version、owner.register(name, service)、
owner.unregister(name)。依赖 maafw.agent_env.v1。
0.1.0 是联调版本,已知取舍见本包所在仓库的拆分契约文档。环境变量 AUTO_MAS_MFW_NO_CLEANUP=1
时插件不跑任何维护清理(联调保护)。
开发时把本目录联接到宿主的 plugins/maafw_project_update,通过插件中心加载。
Metadata
Release files for auto-mas-maafw-project-update 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| auto_mas_maafw_project_update-0.2.0.tar.gz | 387.5 kB | With provenance | Details for auto_mas_maafw_project_update-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| auto_mas_maafw_project_update-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for auto_mas_maafw_project_update-0.2.0-py3-none-any.whl |
Total release size: 827.7 kB
Release files / auto_mas_maafw_project_update-0.2.0.tar.gz
| Download URL | auto_mas_maafw_project_update-0.2.0.tar.gz |
|---|---|
| Size | 387.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd1a3a27d2e15df5319315bfceed8139fa9cc5553f24ab42d33fe45128e84179
|
|
BLAKE2b-256 checksum How to use checksums |
b434dd4460c6cbc881838a50f2a7ebc586cae491f9c1af569debbf7f37f502bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logRelease files / auto_mas_maafw_project_update-0.2.0-py3-none-any.whl
| Download URL | auto_mas_maafw_project_update-0.2.0-py3-none-any.whl |
|---|---|
| Size | 440.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1e7e4293c0333f8dbb2f86cbbc27da6fac521536143d7e5e00c3b9a66de7eea
|
|
BLAKE2b-256 checksum How to use checksums |
70ff266a5b6dba899bcea51e33da7b0a426a9d530955a8f40ce62a4f5f46810f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logSecurity for auto-mas-maafw-project-update 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for auto_mas_maafw_project_update-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.