chore: remove runtime_ci_tooling dev_dependency#10
Merged
tsavo-at-pieces merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
…n CI) runtime_ci_tooling is globally activated via dart pub global activate in CI pipelines — it should not be a dev_dependency. Having it as a git dep causes workspace resolution conflicts when the package is also a workspace member in the monorepo. Made-with: Cursor
There was a problem hiding this comment.
Pull request overview
Removes runtime_ci_tooling from dev_dependencies in pubspec.yaml because the tool is already installed/used via global activation in CI, resolving a workspace dependency resolution conflict.
Changes:
- Deleted the git-based
runtime_ci_toolingentry fromdev_dependencies. - Added inline guidance in
pubspec.yamlto usedart pub global activate/runforruntime_ci_tooling.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+15
to
+17
| # runtime_ci_tooling — use global activation (do not add as a dev_dependency). Example: | ||
| # dart pub global activate --source git https://github.com/open-runtime/runtime_ci_tooling.git --git-ref vX.Y.Z | ||
| # dart pub global run runtime_ci_tooling:manage_cicd --help |
There was a problem hiding this comment.
The repository docs still state that runtime_ci_tooling is used as a dev_dependency (e.g., README.md "Contributing" section). Since this PR removes it from pubspec.yaml, those docs should be updated in the same change to avoid misleading contributors about how to run/manage CI tooling locally.
| tag_pattern: "v{{version}}" | ||
| version: ^0.23.0 | ||
| # runtime_ci_tooling — use global activation (do not add as a dev_dependency). Example: | ||
| # dart pub global activate --source git https://github.com/open-runtime/runtime_ci_tooling.git --git-ref vX.Y.Z |
There was a problem hiding this comment.
The activation example uses a placeholder --git-ref vX.Y.Z, but the CI workflows in this repo pin a specific runtime_ci_tooling version. Consider referencing the pinned version (or pointing to where it is defined) so developers don't accidentally use a mismatched tooling version when regenerating workflows.
Suggested change
| # dart pub global activate --source git https://github.com/open-runtime/runtime_ci_tooling.git --git-ref vX.Y.Z | |
| # dart pub global activate --source git https://github.com/open-runtime/runtime_ci_tooling.git --git-ref <TAG_PINNED_IN_CI> # Use the same tag as pinned in the CI workflows |
tsavo-at-pieces
pushed a commit
that referenced
this pull request
Mar 26, 2026
## Changelog ## [1.1.4] - 2026-03-26 ### Changed - Removed `runtime_ci_tooling` from `dev_dependencies` since it is globally activated in CI pipelines, resolving workspace resolution conflicts (#10) ## Files Modified ``` .../audit/v1.1.4/explore/breaking_changes.json | 4 ++ .../audit/v1.1.4/explore/commit_analysis.json | 22 ++++++ .runtime_ci/audit/v1.1.4/explore/pr_data.json | 15 ++++ .runtime_ci/audit/v1.1.4/meta.json | 82 ++++++++++++++++++++++ .../v1.1.4/version_analysis/version_bump.json | 3 + .../version_analysis/version_bump_rationale.md | 18 +++++ .../release_notes/v1.1.4/changelog_entry.md | 4 ++ .runtime_ci/release_notes/v1.1.4/contributors.json | 5 ++ .runtime_ci/release_notes/v1.1.4/highlights.md | 3 + .../release_notes/v1.1.4/linked_issues.json | 12 ++++ .runtime_ci/release_notes/v1.1.4/release_notes.md | 38 ++++++++++ .../release_notes/v1.1.4/release_notes_body.md | 38 ++++++++++ .runtime_ci/version_bumps/v1.1.4.md | 18 +++++ CHANGELOG.md | 6 ++ README.md | 4 +- pubspec.yaml | 2 +- 16 files changed, 271 insertions(+), 3 deletions(-) ``` ## Version Bump Rationale # Version Bump Rationale **Decision**: patch This release addresses a maintenance task, specifically the removal of the `runtime_ci_tooling` package from `dev_dependencies` in `pubspec.yaml`. This package is now globally activated in CI pipelines, and having it as a git dependency caused workspace resolution conflicts when the package is also a workspace member in the monorepo. This does not affect the functionality or public API of the package. **Key Changes**: * Removed `runtime_ci_tooling` from `dev_dependencies` to resolve monorepo workspace conflicts. **Breaking Changes**: * None. The change is restricted to development workflow metadata and internal tooling dependencies. **New Features**: * None. **References**: * Merge pull request #10 from open-runtime/chore/productionize-agentic-systems * Commit: `chore: remove runtime_ci_tooling dev_dependency` ## Contributors - @tsavo-at-pieces --- Automated release by CI/CD pipeline (Gemini CLI + GitHub Actions) Commits since v1.1.3: 2 Generated: 2026-03-26T21:16:20.245129Z
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
runtime_ci_tooling is globally activated in CI — not a dev_dependency. Removes workspace resolution conflict.
Made with Cursor