Repository navigation
ci: restore Executor 1.4.6 dev archive to GitHub Release - #91
Closed
sanikolaev wants to merge 1 commit into
Closed
sanikolaev wants to merge 1 commit into
sanikolaev wants to merge 1 commit into
Conversation
Reuse the archived Linux AMD64 development tarball from the original dev packaging run and attach it to the existing GitHub release. No rebuilding, publishing, tag changes, or runtime changes.
sanikolaev
force-pushed
the
ci/rebuild-executor-146-dev-remove-release-tag
branch
from
October 24, 2026 05:23
fa00bee to
eb434bd
Compare
sanikolaev
changed the title
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.
The original Executor dev build run #39895724555 already published all 29 Debian, RPM and macOS
1.4.6+26102310-445049b4-devpackages to thedevrepositories. That run only failed its final dependency-update job, because it referenced the renamed Manticore Searchmasterbranch.Therefore no rebuilding and no republication of packages is needed. Manticore Search's PR #5028 now pins the existing dev package and reverts the temporary
release_candidatefallbacks.The only missing item is the matching
manticore-executor-1.4.6+26102310-445049b4-dev-linux-amd64-dev.tar.gzasset required by Test Kit. The original run's archive remains available as the Actions artifactartifact-dev-ubuntu-22.04-amd64, but a later release job recreated Release1.4.6, so the current release contains only thea57785f2archives.This PR adds a temporary, manually triggered workflow which downloads the already-built archive from run
39895724555and adds only the missing asset to the existing GitHub Release1.4.6. It does not build anything, change tags, replace existing release assets, or publish any packages.After merging: Actions → Restore Executor 1.4.6 dev test archive → Run workflow, choose
main, and typerestore-executor-1.4.6-dev-archive. Then verify the new asset appears on Release 1.4.6 and run CI for Manticore Search PR #5028. Remove this temporary workflow afterwards.The
release-1.4.6tag can be retained: it does not affectdeps.txtonce Manticore Search is pinned to the published dev build.