Restore LICENSE.txt (wiped by 26.5.0 snapshot-promote)#310
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.
What
Restores
LICENSE.txt(MIT, Aspose Pty Ltd, 2001-2026) which was on main at commit5fe6164b6(Jun 10) but never lived onrelease/26.5.0. The snapshot-promote (8acbf18a) set main's tree to release's tree → wiped the file.Why this happened
Release branches are orphans of main — Phase 2b in
run_version_bump()only seeds.github/from main, nothing else. So files added to main after the release branch is created (like LICENSE.txt was) don't propagate to the release tree, and a snapshot-promote then wipes them from main.Permanent fix is a follow-up MR on the generator (extend Phase 2b to seed a configurable file list; add a pre-promote guardrail that aborts when files would be wiped). This PR just restores what was lost.
Validation
5fe6164b6via the contents API — byte-for-byte identical.csdiff so theBuild & Run changed examplesworkflow will short-circuit