Repository navigation
CI: re-point the automation at the 1.6.0 branches - #48
Merged
Merged
Conversation
dev-branch and stable carry 1.6 since the 1.6.0 release. Retire the advisory "upgrade from dev-branch" leg, which now tests 1.6 against itself. Stop appending the working-1.6 beta version to advisories. Point the API validation default and the install-test example at dev-branch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pull_request self-test fell back to api-paging-limits, a fogproject branch that no longer exists, so the clone failed with exit 128. 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.
FOG 1.6.0 moved
master,stable,dev-branchandrc-1.6.0to one commit (e445a422e). This is Phase E ofdocs/release/1.6.0-release-runbook.md.fogproject-tests.yml: the 1.5 upgrade check runs only fromstable(pinned to1.5.10.2534by the tree under test). The advisorydev-branchleg is gone. dev-branch is 1.6 now, so that leg upgraded 1.6 to 1.6. It was never a required context.stable-releases.yml: the advisory step no longer appends theworking-1.6badge as a beta patched version.$TAGis a 1.6.0.N version now, andworking-1.6is deleted at the 11 Dec run.reusable_api_validation.yml: the default ref isdev-branch, notworking-1.6.branch_install_test.yml: the input example saysdev-branch.update-lang-fix-psr-and-sync-version.ymlstill listsworking-1.6. That branch exists until the grace window ends, so it stays until the Phase F sweep.🤖 Generated with Claude Code