summer build always emitted party.Describe and []party.Info, so an
application whose framework requirement predates v0.6.0 stopped compiling
once the CLI was updated. The build now checks the party package go list
resolves in the application (a static look for Describe and Info, not a
version compare, since a local checkout reports the previous tag until
it is tagged) and, when they are missing, writes main.go and
plugins.gen.go exactly as before, with a warning to move the framework
to v0.6.0. An unresolvable party package keeps the current sources.
- TestPluginDirs and TestEffectiveFramework over go list JSON fixtures and
git checkouts; TestResolveInstall against an in-memory registry;
TestAppendManifestPlugins for the in-place summer.yaml edit
- fix: a package of the application's own module was reported as a
submodule with the application's git describe; it is in-app (local)
- fix: summer.yaml items written as '- id:' keep their spacing when
plugin:add or plugin:install appends to them
- party.Info, party.Installed, party.Describe (additive; Plugin and Activate unchanged)
- summer build resolves plugin dirs with one go list, reads plugin.yaml, versions per D-07 (module version, git describe without --dirty, none for in-app plugins)
- build.EffectiveFramework: newest tag of a locally replaced or used framework checkout, else the go.mod require
- generated main calls party.Describe(app, PluginInfo, FrameworkVersion) before Activate; metadata failures warn and fall back to IDs
- summer new goldens and examples/hello regenerated
