pantheon-systems / pantheon-systems/phpcompatibility-action
v2: Stop updating major-version branch
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 9
- Forks
- 5
- Avg merge
- 4h 34m
- Merged PRs (30d)
- 2
Description
Summary
Stop creating/updating the floating v1 major-version branch on release. Consumers should pin by SHA with an exact version tag comment instead.
This is a breaking change for consumers currently pinned to @v1 (the branch), which is why it belongs in a major version bump. Consumers pinned by SHA are unaffected.
Work
- Remove or disable the major-version branch update from the release workflow
- Update documentation to recommend SHA pinning:
uses: pantheon-systems/phpcompatibility-action@<sha> # v2.0.0 - Leave existing
v1branch in place — it just stops being updated
Context
- Jira: SITE-5949
- Epic: SITE-5932
- Background: scratchpad PR #331, release-pipeline-actions-plan.md item 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the release workflow that creates or updates the floating v1 branch, then find the documentation showing version references. Disable only the branch update, leave the existing branch intact, and update examples to recommend SHA pinning with an exact version comment. Confirm the workflow no longer updates v1 and the documentation uses the new format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100