Archived
docs: record successful main image pull
This commit is contained in:
1 parent
61108185f0
commit
60d7805133
1 file changed
+3
-3
+3
-3
@@ -9,9 +9,9 @@ Spec 001 is implemented on `main`. The next product step is spec 002 (web UI). I
|
||||
|
||||
## Product and engineering backlog
|
||||
|
||||
- [ ] After merging spec 006, configure a Docker-capable Gitea runner and package-write Actions secrets,
|
||||
then verify a main-branch publish, a version-tag publish and a pull of the published image. Only
|
||||
then mark spec 006 implemented.
|
||||
- [ ] Verify a `vX.Y.Z` push publishes both its version tag and `latest` during the next planned
|
||||
release, then mark spec 006 implemented. The `main` image was published and pulled successfully
|
||||
after commit `6110818`.
|
||||
- [ ] Decide whether a persistent directory rule may target the document root. Current sources require
|
||||
a named child directory.
|
||||
- [ ] Investigate whether Recoll's Python binding exposes a native numeric relevance score. The API
|
||||
|
||||
Reference in new issue
Block a user