dev/release#17 - Synchronize version#s for core and core-extensions #20303
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.
Overview
This simplifies the management of version-numbers for core extensions.
See also: https://lab.civicrm.org/dev/release/-/issues/17
Before
Each core-extension has its own version-number. These are often neglected (e.g. not incremented in tandem with the main release).
After
Whenever we update the version-number for
civicrm-core
, it will also update the version-numbers for each core extension.Comments
Some core extensions are in an alpha/beta stage. Currently, for a user who browses the list of available extensions, the "Version" column signals this. However, if the version-numbers are sync'd, then this will no longer provide that signal.
A parallel PR (#20302) updates the extension UI so that the
<develStage>
is communicated more effectively.ping @colemanw