Skip to content

v1.1.2 — Dynamix Artwork Archive

Choose a tag to compare

View all tags
@FridrichMethod FridrichMethod released this 13 Oct 02:10
· 40 commits to main since this release
v1.1.2
1bed861

Maintenance release of the Dynamix artwork archive. The archived files are the same as in v1.1.1. This release closes the low-severity findings of the v1.1.1 pre-release review: a re-run of part of the Pages workflow can no longer deploy, a run fails when its tag names another commit on GitHub at the approval or build job's check, and the documentation checks are pinned by samples.

Browse: searchable gallery · slideshow

Archive contents

  • Originals: every original file, the catalog and the source manifests are byte-identical to v1.1.1.
  • Fetchers: none was run for this release.
  • No new download is attached. dynamix-artwork-archive-v1.0.0.zip still holds every original file.

Deployment

  • Re-runs: the approval job now records the run's attempt next to the commit it approved, and the deploy job runs only when that record is from the current attempt. A re-run of the deploy job alone, or of any jobs without the approval job, deploys nothing, and it fails in a new last job, "Re-run check", with an error that says so. Re-run the whole run ("Re-run all jobs") instead. No permission was added.
  • Moved tags: actions/checkout fetches the tag at the run's commit, so the checkout alone cannot show a tag that was moved after the run started. The approval and build jobs now also read the tag from GitHub with one git ls-remote, without credentials and limited to 60 seconds, and fail closed when it names another commit, is missing or cannot be read. A tag moved after the build job's check is not seen; the run then deploys the commit that every check passed.
  • Runs on v1.1.1: a run takes the Pages workflow from its tag's commit. The github-pages environment still accepts v1.1.1, whose workflow looks the Release up but has neither of the two checks above, so re-run a run on v1.1.1 whole too. Runs on tags before v1.1.1 stay refused at the environment.
  • Unchanged: publishing a Release still deploys its tag's commit after the full test workflow passes on it, and the approval job and the build job each still look up the tag's Release. Pushes, pull requests and schedules never deploy.

Checks

  • Documentation wording rules: every alternative of the release, count and attribution wording rules in the documentation tests is now pinned by a sample or removed as equivalent, except four fillers whose deletion changes nothing. The rules also read code spans by CommonMark's backtick rule, see a date that is bold or written next to Chinese text, and take a condition listed with 、 as one condition only where it is one.
  • Tests: the release gate tests and the release state tests have their own modules. Further tests pin the attempt record, the tag check against GitHub and the README sentences about both.

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.
  • Documentation checks: a 、 written where a ， belongs, between a condition and a statement that the release variable is unset, reads as a list of conditions, so such a sentence is not refused. Some paraphrases of retired wording are not caught either.
  • Details: see the validation 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.1 完全相同。本版本修复 v1.1.1 发布前代码审查中的低严重度问题。

  • 部署：
    • 批准任务现在会把本次运行的尝试（attempt）和它批准的提交一起记录下来，部署任务只在该记录属于当前这次尝试时运行。只重新运行部署任务，或重新运行不含批准任务的任何任务，都不会部署任何内容，并会在新增的最后一个任务“Re-run check”中以说明原因的错误失败；应重新运行整次运行（“Re-run all jobs”）。没有新增任何权限。
    • actions/checkout 会按本次运行的提交取回标签，单看检出内容发现不了运行开始后被移动的标签。批准任务和构建任务现在还会用一次不带凭据、限时 60 秒的 git ls-remote 从 GitHub 读取该标签；标签指向其他提交、不存在或读取失败时，运行都会失败关闭。构建任务检查之后才被移动的标签不会被发现，此时运行部署的是通过了所有检查的那个提交。
    • 运行使用标签所指提交中的工作流。github-pages 环境仍接受 v1.1.1，它的工作流会查询 Release，但没有上面两项检查，因此在 v1.1.1 上的运行也应整次重新运行。v1.1.1 之前的标签仍会被环境拒绝。
  • 检查： 文档测试中关于发布、数量和署名的措辞规则，除四个删去后行为不变的填充项外，每个备选项都有样例固定，或作为等价项删除；这些规则还会按 CommonMark 的反引号规则读取代码片段，能识别加粗的日期和紧挨中文书写的日期，并且只在确实是一个条件时，才把用 、 列出的多项当作一个条件。
  • 已知缺口： Google Play 图库与 Bilibili 缺少 params.mid 的种子仍需在线访问才能确认；在条件和"变量未设置"之间把 ， 写成 、 时，句子会被当作条件列表，因而不会被拒绝。

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

Assets 2
Loading