Repository navigation
fix(update): panels update from published releases only - #129
Merged
Merged
Conversation
The panel's Update followed `agenthits-dev`, which moves with every merge into AgentHits-Dev, so a click on Update installed whatever was merged last, release or not. A release now also moves `agenthits-stable`: after the GitHub release is published, the new `agenthits-stable-tag.yml` workflow copies the release's manifest to that tag (`imagetools create --prefer-index=false`, same digest, no rebuild) and checks the copy byte for byte. A manual run with an older release moves the channel back to it. GHCR retention never deletes the tag. The panel's update check and Update now follow `agenthits-stable` by default. A panel running a build made after the newest release (agenthits-vX.Y.Z-N-g…) is not offered that older release, because its database may already carry the build's migrations; a newer release, or a rebuilt image of the same release, is still offered. DOKPLOY_AGENTHITS_UPDATE_TAG=agenthits-dev keeps a test panel on every build. A missing tag only makes the check report no update. install-agenthits.sh and update.sh still default to `agenthits-dev`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Зачем
Кнопка Update в панели ставила
agenthits-dev, а этот тег сдвигается после каждого мержа вAgentHits-Dev. Поэтому нажатие Update ставило последнее влитое изменение, даже если его ещё не выпускали. Так панель несколько раз оказывалась на невыпущенной сборке.Что изменилось
agenthits-vX.Y.Zиagenthits-devAgentHits Stable Tagставит на тот же манифест тегagenthits-stableagenthits-dev, то есть за каждой сборкойagenthits-stable, то есть только за релизамиagenthits-vX.Y.Z-N-g…)agenthits-devиbuildcacheagenthits-stableПодробности:
docker buildx imagetools create --prefer-index=false), поэтому digest тот же. Workflow побайтно сверяет копию с релизом.AgentHits Stable Tagс более старым релизом откатывает канал обновлений на него. Без указания релиза берётся последний.DOKPLOY_AGENTHITS_UPDATE_TAG=agenthits-devу сервисаdokploy.install-agenthits.shиupdate.shпо-прежнему ставятagenthits-dev. Перевести их на релизы — отдельный шаг: уupdate.shсвоя логика сравнения, и ей нужна такая же защита от отката.Проверки
agenthits-vX.Y.Z[-N-g…]: 8 случаев, включая1.10против1.9и нераспознанные версииagenthits-stableи переопределение наagenthits-devagenthits-v1.1.0(--dry-run)tscдляapps/dokployиpackages/server, biomeapps/dokployvector-validate.test.tsбывают только на Mac (локальный Docker не видит временную папку теста), в CI этот тест проходитЧто сделать после мержа
AgentHits Stable Tagбез параметров, чтобыagenthits-stableсразу указал наagenthits-v1.1.0. Иначе тег появится только со следующим релизом, а до этого проверка обновлений на панелях с этим изменением будет показывать «обновлений нет».🤖 Generated with Claude Code