* feat(mcp): release and version mcp server alongside cli and brain
Wire the MCP server package into the release pipeline so it is published
and version-synced with the cli and brain packages. Add a
replace-mcp-version generator (invoked by auto-increment-version for
nightly and prepare-manual-release for manual), a release-mcp script,
and sync the package to the current alpha version.
Also drop the orphan scope:core tag from release-ui and list mcp in the
PR template's affected-packages section.
* refactor: document release schemas and harden version error handling
Fill in the empty titles and descriptions on the release generator and
executor schemas, and declare the newVersion option so the version
generators are self-documenting and CLI-invocable.
Make the version generators throw with actionable messages instead of
silently logging and returning, validate the brain version format in
auto-increment-version, and fix the misleading source-of-truth message
in replace-ui-version.
* fix: prevent shell injection in npm publish and correct version flag hints
Validate the TAG dist-tag and publish via execFileSync with an argument
array instead of interpolating it into a shell string, removing a
shell-injection vector in the npm-publish executor.
Correct the version generators' error messages to reference the actual
--newVersion / --new-version flag rather than the reserved --version.
* chore: lint and cleanup of touched files
* build: add executor to replace version for ui libs
this executor finds all package.json in the libs/ui directory
and replaces the current version
of @spartan-ng with the one defined in UI_VERSION
* build: update cli files to reflect new versions and add scripts to make publishing easier
* chore: fix linting errors
* build: update semantic release config
* build: use same VERSION env var for ui and cli
* fix: remove confusing comment
* fix: add regex only updating spartan specific versions
and a unit test to make sure we don't accidentally mess with other packages
* fix: remove .DS_Store files and filter helm packages to not add them to package.json
* chore: remove unused script
* chore: add generator that auto-increments current version of released assets
* chore: add scripts for nightly release
* chore: add nightly release workflow
* fix: add missing dash
* chore: try on push for testing
* build: auto fix version number in tools
* ci: set up automatic release and committing of changed files
* ci: give release step write permissions
* ci: check out branch correctly so we can commit it back
* ci: try to push to right place
* chore: reorder package.json
* fix: use newVersion to allow for auto increment script to work
* chore: update branch name
* fix: rename release scripts and interface and add missing generators
* chore: release cli & ui 0.0.1-alpha.379
* chore: fix name for trigger
* chore: try to push to origin nightly-release
* chore: nightly release 2024-12-10 ⚡
* chore: update tools version number
* chore: nightly release 2024-12-10 ⚡
* chore: update github flow to work on main and a schedule
* fix: add back lost test and start commands to package.json
* fix: fix tests and commit message to follow guidelines
* feat: adjust version replacement for new single brain package
* fix: use correct alpha version 381
* fix: add back storybook command to package.json
* fix: typo in @spartan-ng/brain version for pagination helm
* fix: remove tests that don't do anything and add formatting of files
---------
Co-authored-by: Leonidas <leonidas@spartan.ng>
in the spirit of shadcn ui we want people to own their styles.
this is a first step that allows us to easily turn our internal
hlm directives, components, etc. into templates for nx an nx
generator. Which means that inside an nx workspace you will be
able to simply copy our styles into your own library.
Robin Goetz