Repository navigation
chore: remove release-as after 0.1.0 is published #107
Description
#106 pins the first release of vgv_ai_cli and plugin_source with "release-as": "0.1.0" in .release-please-config.json, because the manifest already recorded 0.1.0 and release-please would otherwise release 0.2.0.
Once v0.1.0 and plugin_source-v0.1.0 are tagged and both packages are on pub.dev, remove both release-as entries, and the reminder comment in .github/workflows/release_please.yaml. Left in place, release-please keeps proposing 0.1.0 instead of bumping from it.
Activity
chore: note when to remove release-as (#107)
[-]chore: remove release-as from .release-please-config.json after 0.1.0 is published[/-][+]chore: remove release-as after 0.1.0 is published[/+]