change: Drop dev-master composer branch alias & update actions branch
#1708
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.
We have renamed the
masterbranch to3.xas part of preparations for working towards a 4.0 release. In future, all main branches will be named for their release series in this fashion.Anyone directly depending on
dev-masterin their owncomposer.jsonwill see a failure on their next composer update. They will need to migrate to a more specific constraint for the actual version they require.Github actions will build on all pushes to a
*.xbranch - we will no longer need to update the workflow when starting a new version series.Fixes #1703