Publish version tags automatically and install the latest release with one command - #208
Merged
Merged
Conversation
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.
Outcome
Pushing a version tag now runs the shared repository checks, builds the existing Linux amd64 distribution, and publishes its matched assets in the same tag's GitHub Release. Prerelease suffixes produce prereleases. Manual runs remain artifact-only or draft-only.
Each release includes a standalone
install.shand checksum. It defaults to the latest stable release, accepts--version, downloads one fixed release's offline archive, verifies it, rejects unsafe extraction paths, and delegates to the existing installer. README, the installation guide and the landing page use the short public installation command. No GitHub login is required.The combined Runtime image also drops retired inner-sandbox files and settings that blocked distribution builds. Native Harness startup checks remain in the image build.
Publication is bound to the Release ID returned by creation. Existing drafts/releases are refused; upload failures and unknown write results preserve state without deletion, overwrite or automatic replay. The tag is rechecked after upload, before publication. Only the publication job has repository write permission.
Boundaries
No image registry publishing, changes to Runtime execution, existing-installation upgrades, private download authentication or new platform support. No real version tag or public Release was created during development.
Validation
make check-distributionpasses remotely; workflow lint and native daemon/installer CI pass on Linux, macOS and Windows.make checkpassed in artifact-only run 36520844816. Later changes are confined to publication, bootstrap, documentation and distribution packaging, covered by focused checks. The first actual image build exposed retired inner-sandbox paths; those are removed.make checkCI also passed: run 36524251964, 29m10s for the job. All final PR checks passed.The first version tag after merge will exercise real GitHub publication and public downloads. Development used artifact-only builds and deterministic API/archive fixtures; no real version tag or Release was created.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.