Skip to content

chore: versionScript to use consistent dependency range prefix#1712

Merged
kdinev merged 2 commits into
masterfrom
dpetev/version-script-range
Jun 1, 2026
Merged

chore: versionScript to use consistent dependency range prefix#1712
kdinev merged 2 commits into
masterfrom
dpetev/version-script-range

Conversation

@damyanpetev
Copy link
Copy Markdown
Member

@damyanpetev damyanpetev commented Jun 1, 2026

Enforce version range for cross-package deps so the release script per https://github.com/IgniteUI/igniteui-cli/wiki/publishing-new-versions#prepare-local-state produces the expected result instead of having to manually adjust those after.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring / code cleanup
  • Build / CI configuration change

Affected Packages

  • igniteui-cli (packages/cli)
  • @igniteui/cli-core (packages/core)
  • @igniteui/angular-templates (packages/igx-templates)
  • @igniteui/angular-schematics (packages/ng-schematics)
  • @igniteui/mcp-server (packages/igniteui-mcp)

Checklist

  • I have tested my changes locally (npm run test)
  • I have built the project successfully (npm run build)
  • I have run the linter (npm run lint)
  • I have added/updated tests as needed
  • My changes do not introduce new warnings or errors

Additional Context

Copilot AI review requested due to automatic review settings June 1, 2026 11:30
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repo’s release/versioning script to enforce a consistent dependency range prefix for cross-package dependencies, so generated package versions and internal dependency ranges don’t require manual adjustment post-run.

Changes:

  • Introduces a shared DEP_RANGE_PREFIX constant and applies it when rewriting internal dependency versions.
  • Adds coreVersion tracking so some internal dependencies (@igniteui/cli-core, @igniteui/mcp-server) are pinned to the core package version rather than the derived Angular templates/schematics version.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coveralls
Copy link
Copy Markdown

coveralls commented Jun 1, 2026

Coverage Status

coverage: 87.927%. remained the same — dpetev/version-script-range into master

@kdinev kdinev merged commit 4b2c032 into master Jun 1, 2026
4 checks passed
@kdinev kdinev deleted the dpetev/version-script-range branch June 1, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants