Repository navigation
Publish preview releases automatically when main updates - #17
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.
Merging a reviewed Vagrant update currently creates no release because publication only listens for v* tags. Add native build and publication on pushes to main, publishing v0.1.0-preview.main. after Linux, Windows and universal macOS packages and downloaded checksums all pass. Each automatic release tag points to the exact merged commit.
Use one shared build version for archives and publication. Main revisions have distinct concurrency groups, so later merges do not replace an earlier pending preview. PR updates retain cancellation within their PR group and never publish. Manual artifact runs and manually versioned tags remain supported; tag-based releases retain verify-tag and use the tag's own version.
Update release notes for the audited public engine SDK, dialogue repair and opening presentation fixes, and document the new automatic-preview behavior.
Validation: actionlint and diff checks pass. The actual publication shell was exercised with a recording gh command for both main and tag contexts: both attach all six archives/checksums; main targets the exact commit, while manual tags require verify-tag. Native Linux, Windows and universal macOS package CI all passed; the release job was correctly skipped for the PR: https://github.com/RakuenSoftware/vagrant/actions/runs/43747181286. No player images were built locally. The separately tagged v0.1.0-preview.11 release is published from merged PR #16, with all three native builds and release checksum verification passed: https://github.com/RakuenSoftware/vagrant/releases/tag/v0.1.0-preview.11.