refactor because versioning data should be handled by Collection, not Pod::From::Cache
git type commands to get repo level and per-file versioning data is passed from a config option
the data is generated in the Post-Cache role, which is in Collection
the per-file data is added to the PodFile instance when the source is rendered, as part of the PodFile.config data
debug-when & verbose-when were modified to take a sequence from a string, not just one file name. In line with with-only
the per-file data can be accessed directly as PodFile config data is automatically made available via the %prm<config> parameter.
the config files of the Collection and the templates will need to be changed.
good versioning data will not be available unless the method add-versioning-data is called so calling for versionning will generate unknown or Not available rather than throwing exceptions to ensure some backwards compatibility
distinguish between 'plugin' and 'callable' at a milestone for that plugin.
remove references to Cleanup milestone, which was never used.
add a list of milestones towards the top.
add Collection::RefreshPlugins
add collection-refresh-plugins
remove plugins key for mode config (The ability to add arbitrary names was designed to allow for the multiple use of plugins. This specification has changed. Now plugins are released with semantic versioning, and plugins are released for each Major version. Updating is done via the plugins.conf file.
plugin-format is now added as a mandatory key for Mode configuration
honour no-status in preserve-state
finished refresh-plugins, finalised format for 'plugins.rakuon'
tests added
define Modes to be named like plugins without '_', thus allowing sub-directories within a collection not to be Modes, use-case, _local_raku_docs as a git repo.
change METADATA key in plugins.rakuon to metadata to take advantage of this
include check for default released dir before asking for new one in Refresh
fixed the anomalous exit after git cloning
revise report plugin spec so that one plugin can produce multiple report files
report plugin returns an Array of Pairs, not just a Pair
change test accordingly
revise post-cache documentation
change no-report & no-completion to without-* to be consistent with without-processing
remove no-cache, as its not in get-config
Revise milestone handling
collect process can be stopped before AND after each stage
change :end to :after to be compatible with :before
:after implies no plugins triggered for a milestone, before implies plugins triggered
dump-at implies plugins triggered
change tests to reflect new specifications
milestone information object includes plugins-used array of hashes
revise README documentation