Skip to content

v1.1.1 — Dynamix Artwork Archive

Choose a tag to compare

View all tags
@FridrichMethod FridrichMethod released this 12 Oct 12:24
· 93 commits to main since this release
v1.1.1
4bf73a2

Maintenance release of the Dynamix artwork archive. The archived files are the same as in v1.1.0. This release tightens the deployment checks and the catalog schema, and closes the remaining minor findings of the independent review that do not need live access.

Browse: searchable gallery · slideshow

Archive contents

  • Originals: every original file, the catalog and the source manifests are byte-identical to v1.1.0.
  • Fetchers: none was run for this release. The fetcher and classification changes below apply to future runs.
  • No new download is attached. dynamix-artwork-archive-v1.0.0.zip still holds every original file.

Deployment

  • Release check: every run now checks that its tag has a published GitHub Release that is not a prerelease. The approval job, and again the build job, each make one read-only request to the GitHub API for it. This applies to a release run, to a dispatch and to a re-run. The run is refused on any other answer: no Release, a draft, a prerelease, a Release of another tag, an error or an unreadable answer.
    • A re-run keeps the event of the run it repeats, so a release run that is re-run after its Release became a draft or a prerelease, or was deleted, is refused. A re-run of the deploy job alone repeats no Release lookup, so re-run the whole run.
    • A run takes the workflow from its tag's commit. A run on a tag before v1.1.1 would use that tag's own workflow, which does not make this check; the github-pages environment refuses its deployment (see below).
  • Tag form: a vX.Y.Z tag has three numbers without leading zeros. v1.10.0 is accepted; v1.02.0 and v01.1.0 are refused.
  • Prerelease flag: the deploy job's own condition now also refuses a release event without a prerelease flag, as the approval and build jobs already did.
  • Approved commit: the deploy job runs only for the commit that the approval job recorded.
  • Tag ruleset and environment: a repository ruleset, "Release tags v*", lets only repository admins create, move or delete v* tags. The github-pages environment now accepts deployments only from tags from v1.1.1 on, and no longer from main. A run takes the Pages workflow from its tag's commit, so the two keep anyone but an admin from deploying through the github-pages environment with a workflow of their own.
  • Unchanged: publishing a Release still deploys its tag's commit after the full test workflow passes on it. Pushes, pull requests and schedules never deploy.

Fetchers and checks

  • Catalog schema (review finding DX2-07). All committed data passes these rules.
    • An accepted candidate (downloaded or duplicate_bytes) must carry game evidence.
    • apple_store, google_play, taptap_app and page_links seeds must give identity_quotes, since their game evidence comes from them.
    • The rule that a credit's evidence names a member of the matching credit list applies to family manifest records too.
    • Every credit entry in the catalog needs a URL or a quote.
  • Page links: "Also linked from" notes are compared whole, so a page now gets its own note even when an already noted page's URL extends its URL (https://x/a beside https://x/a.html).
  • Wiki captions: after the bare game name and a comma, an occasion of a listed game ("Artwork in Dynamix, Lanota Collaboration") now records that game, as the dash form already did. Other text after the comma, such as a credit, is left out of the name as before. No committed caption changes classification.
  • Tests: further tests pin the deployment guard, the documentation wording rules, the caption rules and the seed checks.

Known gaps

  • From v1.0.0: the access gaps recorded at v1.0.0 remain, since no source was refetched.
  • Live access needed: two adapter cases cannot be settled without it.
    • A Google Play gallery layout.
    • The Bilibili seed with no params.mid. Its v1.0.0 read was blocked by a challenge. Until its account ID is recorded, any picture read from it is held for review.
  • Pre-release review: its low-severity findings are left for v1.1.2. Among them, a re-run of the deploy job alone repeats no Release lookup; re-run the whole run instead.
  • Details: see the validation report and the coverage report.

Rights

The software is licensed under Apache-2.0 (see LICENSE and NOTICE). The interface is adapted from the DEEMO gallery by Mashiro and FridrichMethod (FridrichMethod/deemo). Dynamix artwork and other game assets remain © C4Cat Entertainment Limited and/or the credited artists; the software license grants no rights to these media. See the license and attribution index.

简体中文： Dynamix 曲绘档案的维护版本，原文件与 v1.1.0 完全相同。

  • 部署：
    • 每次运行（发布触发、手动触发或重新运行）都会检查该标签是否有已发布、非预发布的 GitHub Release：批准任务和构建任务各向 GitHub API 发出一次只读请求，其他任何结果都会拒绝运行。只重新运行部署任务时不会再次查询 Release，因此应重新运行整次运行。
    • 运行使用标签所指提交中的工作流，v1.1.1 之前的标签不做这项检查；github-pages 环境现在只接受 v1.1.1 及之后的标签（不再接受 main），会拒绝这类运行的部署。
    • 标签的三个数字不能有前导零（v1.10.0 可以，v1.02.0 不行）。
    • 部署任务自身的条件现在也拒绝缺少预发布标记的 Release 事件（此前已由批准任务和构建任务拒绝）；部署任务只部署批准任务批准的提交。
    • 仓库规则集 "Release tags v*" 只允许仓库管理员创建、移动或删除 v* 标签。
  • 目录检查： 已接受的候选项必须有游戏证据；靠身份文字取证的种子必须提供 identity_quotes；署名证据须指向对应署名列表成员的规则也适用于来源清单记录；目录中的每条署名都需要 URL 或引文。已提交的数据全部符合。
  • 图注： "Artwork in Dynamix, Lanota Collaboration" 这种逗号写法现在会像破折号写法一样记录 Lanota；已提交图注的分类没有任何变化。
  • 已知缺口： Google Play 图库与 Bilibili 缺少 params.mid 的种子仍需在线访问才能确认；发布前代码审查的低严重度问题留到 v1.1.2（例如只重新运行部署任务时不会再次查询 Release，应重新运行整次运行）。

美术作品版权归 C4Cat Entertainment Limited 和/或署名画师所有。软件许可（Apache-2.0）不授予这些素材任何权利。

Assets 2
Loading