You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sync the release version into extra files during a release #948
A release unit often stores its version in more places than the one manifest Craft bumps automatically. Right now the only way to keep those files in sync is a custom preReleaseCommand, and setting one turns off Craft's automatic version bump for that unit.
Current behavior (3.6.0)
Automatic bumping only writes the release unit's own manifest.NpmTarget.bumpVersion runs npm version in the release unit directory, plus any npm workspaces under it. It doesn't update a package.json outside that directory, other JSON files, or Markdown/YAML frontmatter.
Automatic bumping only runs without a preReleaseCommand. A unit that needs to update one extra file has to take over the whole bump.
Sets packages/cli/package.json to the version. Craft can already do this.
Sets packages/mcp-server/package.json to the same version. The MCP server ships with every CLI release, but its package lives outside the CLI workspace.
Sets version in plugins/sentry-cli/.claude-plugin/plugin.json with the prerelease suffix removed.
Rewrites the version: line in the YAML frontmatter of plugins/sentry-cli/skills/sentry-cli/SKILL.md and references/*.md. Today this only happens in the post-release step.
Proposal
Let a release unit list extra files to update with the new version, and keep the automatic manifest bump on. Roughly:
Activity
feat(publish): Add built-in development version bump after release (#950