openc3 7.4.0 → 7.5.0

data/lib/openc3/version.rb

@@ -1,14 +1,14 @@
 # encoding: ascii-8bit
 
-OPENC3_VERSION = '7.4.0'
+OPENC3_VERSION = '7.5.0'
 module OpenC3
   module Version
     MAJOR = '7'
-    MINOR = '4'
+    MINOR = '5'
     PATCH = '0'
     OTHER = ''
-    BUILD = 'ed0cb44ca3c661eaf2babb77664d0063c955c68c'
+    BUILD = 'f77108e1b9d90505ae1ba0a893150c837f879288'
   end
-  VERSION = '7.4.0'
-  GEM_VERSION = '7.4.0'
+  VERSION = '7.5.0'
+  GEM_VERSION = '7.5.0'
 end

data/templates/conversion/conversion.py

@@ -1,6 +1,6 @@
 from openc3.conversions.conversion import Conversion
-# Using tlm() requires the following:
-# from openc3.api.tlm_api import tlm
+# Using System.telemetry.packet() requires the following:
+# from openc3.system.system import System
 
 # Custom conversion class
 # See https://docs.openc3.com/docs/configuration/conversions
@@ -20,4 +20,8 @@ class <%= conversion_class %>(Conversion):
         # Used when conversion is applied to a regular (not DERIVED) item
         # NOTE: You can also use packet.read("ITEM") to get additional values
         # return value / 2 * packet.read("OTHER_ITEM")
+        #
+        # In a READ_CONVERSION, read the latest value from a different packet in the same target
+        # other = System.telemetry.packet(packet.target_name, "OTHER_PACKET")
+        # return value * other.read("OTHER_ITEM")
         return value

data/templates/conversion/conversion.rb

@@ -20,6 +20,11 @@ module OpenC3
       # Used when conversion is applied to a regular (not DERIVED) item
       # NOTE: You can also use packet.read("ITEM") to get additional values
       # return value / 2 * packet.read("OTHER_ITEM")
+      #
+      # In a READ_CONVERSION, read the latest value from a different packet in the same target
+      # other = System.telemetry.packet(packet.target_name, "OTHER_PACKET")
+      # return value * other.read("OTHER_ITEM")
+      return value
     end
   end
 end

data/templates/plugin/.github/workflows/playwright.yml

@@ -0,0 +1,62 @@
+# Builds this plugin and installs it into a real COSMOS with Playwright.
+#
+# Runs the most recent COSMOS Core release in Docker, builds the plugin gem, and
+# drives the Admin tool the way an operator would: Install From File, submit the
+# variables dialog, and wait for the install to report Complete. That catches
+# what unit tests can't - a plugin.txt that doesn't parse, a target that doesn't
+# build, a microservice that won't start.
+#
+# Nothing here needs configuring as the plugin grows. Tool pages are discovered
+# from the COSMOS API after install and checked for browser console errors, and
+# a frontend is built with pnpm whenever the plugin has a package.json, so
+# `cli generate tool` and `cli generate widget` are covered with no edit here.
+#
+# Runs on every commit and once a week. The weekly run is what catches a new
+# COSMOS release breaking this plugin. Note that GitHub disables scheduled
+# workflows in a repo with no activity for 60 days.
+
+name: Playwright
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: ["**"]
+  # Off the hour because scheduled runs at :00 get queued behind everyone else's
+  schedule:
+    - cron: '27 7 * * 1'
+  workflow_dispatch:
+    inputs:
+      cosmos_version:
+        description: 'COSMOS version to run, or latest'
+        required: false
+        type: string
+        default: 'latest'
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  # Superseding a pull request run is fine, but a scheduled run and a push to
+  # main share a ref, so cancelling on those would have them kill each other
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  playwright:
+    uses: OpenC3/.github/.github/workflows/plugin-playwright-reusable.yml@main
+    with:
+      plugin_directory: .
+      cosmos_version: ${{ inputs.cosmos_version || 'latest' }}
+      # Once you have added targets with `cli generate target`, list them here
+      # and the install is checked for them:
+      # expected_targets: MY_TARGET ANOTHER_TARGET
+      #
+      # install_demo: true  # Uncomment if this plugin references INST/INST2
+      # is_tool: true  # Uncomment to require that this plugin registers a tool
+      #
+      # Tool pages are checked for browser console errors automatically. Add
+      # regexes here for errors to allow:
+      # console_ignore: |
+      #   some third party gripe
+      #   another known message

data/templates/plugin/.github/workflows/release.yml

@@ -0,0 +1,45 @@
+# Builds the gem, tags the commit, and creates a GitHub release. Run it by hand
+# from the Actions tab and give it a version number.
+#
+# Both publish steps are off by default so a first release works with no setup
+# at all. Tick the box in the run dialog when you are ready to publish, after
+# adding the matching secret to the repo:
+#
+#   Deploy to OpenC3 App Store  ->  OPENC3_API_TOKEN  (your store account token)
+#   Publish the gem to RubyGems ->  RUBYGEMS_API_KEY  (your RubyGems API key)
+#
+# A tool or widget frontend needs nothing set here: once the plugin has a
+# package.json it is built with pnpm before the gem is packaged.
+
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version number'
+        required: true
+        type: string
+      deploy_to_store:
+        description: 'Deploy to OpenC3 App Store'
+        required: false
+        type: boolean
+        default: false
+      deploy_to_rubygems:
+        description: 'Publish the gem to RubyGems'
+        required: false
+        type: boolean
+        default: false
+
+jobs:
+  release:
+    uses: OpenC3/.github/.github/workflows/release-cosmos-plugin-reusable.yml@main
+    with:
+      version: ${{ inputs.version }}
+      deploy_to_store: ${{ inputs.deploy_to_store }}
+      deploy_to_rubygems: ${{ inputs.deploy_to_rubygems }}
+      plugin_directory: .
+      # is_tool: true  # Uncomment to fail the release if package.json is missing
+    secrets:
+      OPENC3_API_TOKEN: ${{ secrets.OPENC3_API_TOKEN }}
+      RUBYGEMS_API_KEY: ${{ secrets.RUBYGEMS_API_KEY }}

data/templates/plugin/.github/workflows/unit-tests.yml

@@ -0,0 +1,35 @@
+# Runs this plugin's unit tests on every push and pull request.
+#
+# Python tests are discovered in tests/ or test/, Ruby specs in spec/ or specs/.
+# Whichever this plugin doesn't have is skipped, so there is nothing to set up:
+# add a test file and it starts running. A plugin with no tests at all passes
+# with a warning until you set require_tests below.
+#
+# Dependencies are picked up automatically - requirements.txt for the code under
+# test, <test dir>/requirements.txt for test only ones, and a Gemfile for Ruby
+# when there is one.
+
+name: Unit Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: ["**"]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  unit-tests:
+    uses: OpenC3/.github/.github/workflows/plugin-unit-tests-reusable.yml@main
+    with:
+      plugin_directory: .
+      # python_version: '3.12'  # Uncomment to pin a different Python
+      # ruby_version: '3.4'  # Uncomment to pin a different Ruby
+      # require_tests: true  # Uncomment to fail the build when there are no tests
+      # gemfile: Gemfile.dev  # Uncomment if the specs need a different Gemfile than the plugin's own

data/templates/plugin/.gitignore

@@ -1 +1,7 @@
 node_modules
+<% if @@language == 'py' -%>
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+<% end -%>

data/templates/plugin/README.md

@@ -8,6 +8,96 @@ Update this comment with your own description.
 
 1. Edit the .gemspec file fields: name, summary, description, authors, email, and homepage
 1. Update the LICENSE.md file with your company name
+<% if @@language == 'py' -%>
+1. Install [uv](https://docs.astral.sh/uv/getting-started/installation/) to manage the plugin's Python dependencies
+
+## Python dependencies with uv
+
+The plugin's Python dependencies are declared in `pyproject.toml` and locked in `uv.lock`.
+Both files are packaged into the gem automatically, and COSMOS reads them when the plugin is installed.
+
+### Adding dependencies
+
+```sh
+uv add requests                 # runtime dependency, installed into COSMOS with the plugin
+uv add --group dev pytest-mock  # development only, never installed into COSMOS
+```
+
+`uv add` updates both `pyproject.toml` and `uv.lock`. Commit both files.
+
+`uv lock` resolves `pyproject.toml` and writes `uv.lock` without installing anything. `uv sync` does the
+same when the lock is stale, then installs into `.venv`. Either works after editing `pyproject.toml` by hand;
+commit the updated `uv.lock`.
+
+COSMOS installs a locked plugin with `uv sync --frozen`, which installs exactly what `uv.lock` records and never
+relocks, so a stale lock ships stale dependencies. `uv lock --check` fails if the lock is out of date.
+
+### How COSMOS installs them
+
+- **With `uv.lock`** (recommended): COSMOS runs `uv sync --frozen --no-dev`. Every install gets the same
+  versions, downloaded from the URLs recorded in the lock.
+- **Without `uv.lock`**: COSMOS resolves the dependencies at install time against the PyPI URL set in
+  Admin Console -> Settings, so versions can change from one install to the next.
+
+The `dev` dependency group is never installed into COSMOS.
+
+### Developing locally
+
+```sh
+uv sync --group dev           # create .venv with runtime and dev dependencies
+uv run --group dev pytest     # run tests; lib/ is on the import path
+uv run --group dev ruff check # lint
+uv run --group dev ruff format
+uv run --group dev ty check   # type check
+```
+
+A plain `uv sync` installs only the runtime dependencies, matching what COSMOS installs.
+
+The plugin itself is not installed into `.venv`: COSMOS puts `lib/` on the Python path instead, and pytest and ty
+are configured to do the same. Anything else needs `lib/` on the path to import `<%= package_name %>`:
+
+```
+PYTHONPATH=lib uv run python my_script.py
+```
+
+`cli generate` writes a `.python-version` file pinning the Python version of the COSMOS image it ran in, so
+uv develops against the same Python COSMOS runs. If you upgrade to a COSMOS release with a newer Python, update
+it with `uv python pin <version>`. Without that file uv picks any installed Python that satisfies
+`requires-python`.
+
+The `openc3` dev dependency provides the COSMOS Python API for your editor, tests and `ty`. Pin it to the
+COSMOS version you deploy to so they see the same API, e.g. `uv add --group dev "openc3==X.Y.Z"`.
+
+### Where to put Python code
+
+Put Python code shared across the plugin in `lib/<%= package_name %>/`, never directly in `lib/`.
+
+COSMOS adds the `lib/` directory of every installed plugin to the Python path. If two plugins both ship
+`lib/helpers.py`, `import helpers` loads whichever one Python finds first, and the other can't be imported
+at all. A module directly in `lib/` can also hide an installed package of the same name, such as `requests`.
+The `<%= package_name %>` package is named after this plugin, so its modules can't collide.
+
+Import from the package:
+
+```python
+from <%= package_name %>.helpers import Helper
+```
+
+Reference its files by path in plugin configuration, e.g. `INTERFACE MY_INT <%= package_name %>/my_interface.py`.
+
+### Updating dependencies
+
+```
+uv lock --upgrade-package requests  # upgrade one package
+uv lock --upgrade                   # upgrade everything
+```
+
+### Private package indexes
+
+See the comments in the `[tool.uv]` section of `pyproject.toml`. If the COSMOS PyPI URL setting points at
+anything other than public PyPI, COSMOS ignores the plugin's own index settings when it resolves, so a
+package published only to your private index must also be served by that index, or be locked in `uv.lock`.
+<% end -%>
 
 ## Building non-tool / widget plugins
 
@@ -26,19 +116,41 @@ If you don’t have a local node environment, you can use our openc3-node contai
 
 Mac / Linux:
 
-```
+```sh
 docker run -it -v `pwd`:/openc3/local:z -w /openc3/local docker.io/openc3inc/openc3-node sh
 ```
 
 Windows:
 
-```
+```sh
 docker run -it -v %cd%:/openc3/local -w /openc3/local docker.io/openc3inc/openc3-node sh
 ```
 
 1. pnpm install --frozen-lockfile --ignore-scripts
 1. rake build VERSION=1.0.0
 
+## Continuous integration
+
+`.github/workflows/` ships three GitHub Actions workflows that work as soon as
+you push this plugin to GitHub. They call shared workflows from `OpenC3/.github`,
+so the steps stay current without you updating anything here.
+
+- **Unit Tests** - on every push and pull request. Runs Python tests in `tests/`
+  or `test/` and Ruby specs in `spec/` or `specs/`. Whichever you don't have is
+  skipped, so just add a test file.
+- **Playwright** - on every push and pull request, plus weekly. Builds the gem,
+  starts the latest COSMOS release in Docker, and installs the plugin through the
+  Admin tool, which catches a `plugin.txt` that doesn't parse, a target that
+  doesn't build, or a microservice that won't start. The weekly run is what tells
+  you a new COSMOS release broke this plugin. Once you add targets, list them in
+  `expected_targets` so the install is verified against them.
+- **Release** - manual, from the Actions tab. Builds the gem, tags the commit and
+  creates a GitHub release. Publishing to the OpenC3 App Store and to RubyGems is
+  off until you add the matching secret and tick the box.
+
+Adding a tool or a widget needs no change to any of these. All three build a
+frontend with pnpm as soon as the plugin has a `package.json`.
+
 ## Installing into OpenC3 COSMOS
 
 1. Go to the OpenC3 Admin Tool, Plugins Tab

data/templates/plugin/lib/PACKAGE/__init__.py

@@ -0,0 +1,4 @@
+# Python code shared across this plugin lives in this package. COSMOS puts
+# every installed plugin's lib/ on sys.path, so a module placed directly in
+# lib/ can collide with another plugin's module of the same name. Keeping it
+# under this uniquely named package avoids that. See README.md.

data/templates/plugin/plugin.gemspec

@@ -20,7 +20,16 @@ Gem::Specification.new do |s|
     time = Time.now.strftime("%Y%m%d%H%M%S")
     s.version = '0.0.0' + ".#{time}"
   end
-  s.files = Dir.glob("{targets,lib,public,tools,microservices}/**/*") + %w(Rakefile README.md LICENSE.md plugin.txt)
+<% if @@language == 'py' -%>
+  # pyproject.toml and uv.lock must be in the gem for COSMOS to install the
+  # plugin's python dependencies: install only sees files the gem contains.
+  # Globbed rather than listed so the gem still builds before `uv lock` is run.
+<% end -%>
+  s.files = Dir.glob("{targets,lib,public,tools,microservices}/**/*") + %w(Rakefile README.md LICENSE.md plugin.txt)<% if @@language == 'py' %> + Dir.glob("{pyproject.toml,uv.lock}")<% end %>
+<% if @@language == 'py' -%>
+  # Running tests or scripts locally writes bytecode next to the source; keep it out of the gem.
+  s.files = s.files.reject { |file| file.include?('__pycache__') }
+<% end -%>
 
   s.metadata = {
     # These fields are used when you submit your plugin to the OpenC3 Store at store.openc3.com

data/templates/plugin/pyproject.toml

@@ -0,0 +1,119 @@
+[project]
+name = "<%= plugin_name %>"
+version = "0.0.0"
+description = "OpenC3 <%= plugin_name %> plugin Python dependencies"
+readme = "README.md"
+requires-python = ">=3.11"
+# Add your plugin's Python dependencies here, then run `uv lock` and commit the
+# resulting uv.lock so COSMOS installs the same versions every time.
+dependencies = []
+
+[dependency-groups]
+# Development and test only. COSMOS installs plugin dependencies with --no-dev,
+# so nothing here reaches a deployed plugin. Left unpinned on purpose: a bound
+# written into this template would still be here whenever you generated this
+# plugin, holding you on stale tooling. Commit the uv.lock for reproducible
+# versions, and add a pin here only if you need a specific one.
+dev = [
+    "openc3",
+    "pytest",
+    "ruff",
+    "ty",
+]
+
+[tool.uv]
+# This file declares dependencies only — it is not a buildable package. COSMOS
+# loads plugin code from lib/ at runtime and installs with `uv sync --frozen`,
+# so nothing here is ever built and no [build-system] is needed.
+package = false
+
+# Keep the dev group out of a plain `uv sync` so a local install matches what
+# COSMOS installs (it passes --no-dev). Use `uv sync --group dev` while
+# developing, or `uv run --group dev pytest`.
+default-groups = []
+
+# Uncomment to install dependencies from a private PyPI repository.
+# See: https://docs.astral.sh/uv/configuration/indexes/
+#
+# These settings are used whenever uv resolves: when you run `uv lock` yourself,
+# and at install time when no uv.lock is committed alongside this file.
+#
+# They do not always survive installation into COSMOS. When the PyPI URL in
+# Admin Console -> Settings names anything other than public PyPI, the operator
+# has designated an index and COSMOS makes it authoritative: the install passes
+# uv `--no-config --no-sources`, so everything below is ignored and every
+# package is resolved from the operator's index. A dependency published only to
+# your private index then fails to install there, rather than being fetched
+# from it — coordinate with the operator so their index serves it too.
+#
+# A committed uv.lock sidesteps this entirely: COSMOS installs with
+# `uv sync --frozen`, which fetches the exact registry and wheel URLs recorded
+# in the lock and consults no index at all.
+#
+# Indexes are searched in the order listed, before the default index. Mark one
+# `default = true` to replace public PyPI entirely, or list your private repo
+# first and leave PyPI as the default to fall back to it.
+#
+# index = [
+#     { name = "private", url = "https://private-pypi.example.com/simple" },
+#     { name = "pypi", url = "https://pypi.org/simple", default = true },
+# ]
+#
+# Pin internal packages to a specific index. A pin keeps a same-named package on
+# public PyPI from being substituted. Add `explicit = true` to an index to keep
+# it from serving anything other than packages pinned to it.
+#
+# sources = { my-internal-pkg = { index = "private" } }
+#
+# Uncomment for self-signed certificates.
+#
+# allow-insecure-host = ["private-pypi.example.com"]
+
+[tool.ty.environment]
+# COSMOS puts the plugin's lib/ on sys.path at runtime rather than installing it,
+# so ty needs it here to resolve imports between the plugin's own modules.
+extra-paths = ["lib"]
+
+[tool.pytest.ini_options]
+# Same reason as ty's extra-paths: lib/ is on sys.path at runtime, not installed,
+# so tests need it on the path to import the plugin's own modules.
+pythonpath = ["lib"]
+
+[tool.ty.rules]
+# These are artifacts of how COSMOS ships its Python API, not mistakes in your
+# plugin, so they are off rather than "warn": ty exits non-zero on a warning, so
+# "warn" would fail the check just as an error does. Delete a line to opt back
+# in, or silence a single case with `# ty: ignore[rule-name]`.
+#
+# openc3.script re-exports its API through star imports (from .telemetry import *,
+# etc.) with no __all__, so ty cannot see tlm, cmd, send_raw and friends even
+# though they resolve at runtime. unresolved-reference covers using such a name,
+# unresolved-import covers importing one by name. Ruff's F405 flags the same
+# thing if you want it reported.
+unresolved-reference = "ignore"
+unresolved-import = "ignore"
+# Script Runner replaces openc3.script.start() at runtime with its own
+# implementation, which accepts bind_variables. The pip package only ships the
+# stub signature start(procedure_name).
+unknown-argument = "ignore"
+
+[tool.ruff]
+line-length = 120
+# target-version is intentionally absent: ruff infers it from the project's
+# requires-python above, so there is one place to bump the minimum. ty does the
+# same, which is why [tool.ty.environment] sets no python-version either.
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "N", "UP", "B", "W", "C4", "SIM"]
+ignore = [
+    "E402",   # Module level import not at top of file
+    "E501",   # Line too long (handled by the formatter)
+    "F402",   # Import shadowed by loop var
+    "F403",   # Star imports used - the documented way to import the COSMOS API
+    "F405",   # Name may be undefined due to star import
+    "N815",   # Mixed case variable in class scope
+]
+
+[tool.ruff.lint.isort]
+known-first-party = ["openc3"]
+lines-after-imports = 2

data/templates/tool_angular/package.json

@@ -1,6 +1,6 @@
 {
   "name": "<%= tool_name %>",
-  "version": "7.4.0",
+  "version": "7.5.0",
   "scripts": {
     "ng": "ng",
     "start": "ng serve",
@@ -23,7 +23,7 @@
     "@angular/platform-browser-dynamic": "^18.2.6",
     "@angular/router": "^18.2.6",
     "@astrouxds/astro-web-components": "^7.24.0",
-    "@openc3/js-common": "7.4.0",
+    "@openc3/js-common": "7.5.0",
     "rxjs": "~7.8.0",
     "single-spa": "^5.9.5",
     "single-spa-angular": "^9.2.0",

data/templates/tool_angular/pnpm-workspace.yaml

@@ -0,0 +1,16 @@
+# Copyright 2026 OpenC3, Inc.
+# All Rights Reserved.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See LICENSE.md for more details.
+#
+# This file may also be used under the terms of a commercial license
+# if purchased from OpenC3, Inc.
+
+minimumReleaseAge: 1440 # 1 day
+minimumReleaseAgeExclude:
+  # we control these packages, so we don't need to wait to consume them
+  - '@openc3/js-common'
+  - '@openc3/vue-common'

data/templates/tool_react/package.json

@@ -16,7 +16,7 @@
     "@emotion/react": "^11.13.3",
     "@emotion/styled": "^11.11.0",
     "@mui/material": "^6.1.1",
-    "@openc3/js-common": "7.4.0",
+    "@openc3/js-common": "7.5.0",
     "react": "^18.2.0",
     "react-dom": "^18.2.0",
     "single-spa-react": "^5.1.4"

data/templates/tool_react/pnpm-workspace.yaml

@@ -0,0 +1,16 @@
+# Copyright 2026 OpenC3, Inc.
+# All Rights Reserved.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See LICENSE.md for more details.
+#
+# This file may also be used under the terms of a commercial license
+# if purchased from OpenC3, Inc.
+
+minimumReleaseAge: 1440 # 1 day
+minimumReleaseAgeExclude:
+  # we control these packages, so we don't need to wait to consume them
+  - '@openc3/js-common'
+  - '@openc3/vue-common'

data/templates/tool_svelte/package.json

@@ -12,7 +12,7 @@
   },
   "dependencies": {
     "@astrouxds/astro-web-components": "^7.24.0",
-    "@openc3/js-common": "7.4.0",
+    "@openc3/js-common": "7.5.0",
     "@smui/button": "^7.0.0",
     "@smui/common": "^7.0.0",
     "@smui/card": "^7.0.0",
@@ -26,6 +26,7 @@
   "devDependencies": {
     "@babel/core": "^7.25.2",
     "@babel/preset-env": "^7.25.4",
+    "@material/theme": "^14.0.0",
     "@rollup/plugin-commonjs": "^28.0.0",
     "@rollup/plugin-node-resolve": "^15.3.0",
     "@testing-library/jest-dom": "^6.5.0",

data/templates/tool_svelte/pnpm-workspace.yaml

@@ -0,0 +1,20 @@
+# Copyright 2026 OpenC3, Inc.
+# All Rights Reserved.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See LICENSE.md for more details.
+#
+# This file may also be used under the terms of a commercial license
+# if purchased from OpenC3, Inc.
+
+# smui-theme builds its sass load path from require.resolve('@material/dom'),
+# which only finds the sibling @material/* packages in a flat node_modules.
+nodeLinker: hoisted
+
+minimumReleaseAge: 1440 # 1 day
+minimumReleaseAgeExclude:
+  # we control these packages, so we don't need to wait to consume them
+  - '@openc3/js-common'
+  - '@openc3/vue-common'

data/templates/tool_vue/package.json

@@ -1,6 +1,6 @@
 {
   "name": "<%= tool_name %>",
-  "version": "7.4.0",
+  "version": "7.5.0",
   "private": true,
   "type": "module",
   "scripts": {
@@ -11,8 +11,8 @@
   },
   "dependencies": {
     "@astrouxds/astro-web-components": "^7.24.0",
-    "@openc3/js-common": "7.4.0",
-    "@openc3/vue-common": "7.4.0",
+    "@openc3/js-common": "7.5.0",
+    "@openc3/vue-common": "7.5.0",
     "axios": "^1.7.7",
     "date-fns": "^4.1.0",
     "lodash": "^4.17.21",

data/templates/tool_vue/pnpm-workspace.yaml

@@ -0,0 +1,16 @@
+# Copyright 2026 OpenC3, Inc.
+# All Rights Reserved.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See LICENSE.md for more details.
+#
+# This file may also be used under the terms of a commercial license
+# if purchased from OpenC3, Inc.
+
+minimumReleaseAge: 1440 # 1 day
+minimumReleaseAgeExclude:
+  # we control these packages, so we don't need to wait to consume them
+  - '@openc3/js-common'
+  - '@openc3/vue-common'

data/templates/widget/package.json

@@ -1,6 +1,6 @@
 {
   "name": "<%= widget_name %>",
-  "version": "7.4.0",
+  "version": "7.5.0",
   "private": true,
   "type": "module",
   "scripts": {
@@ -8,7 +8,7 @@
   },
   "dependencies": {
     "@astrouxds/astro-web-components": "^7.24.0",
-    "@openc3/vue-common": "7.4.0",
+    "@openc3/vue-common": "7.5.0",
     "vuetify": "^3.7.1"
   },
   "devDependencies": {

data/templates/widget/pnpm-workspace.yaml

@@ -0,0 +1,16 @@
+# Copyright 2026 OpenC3, Inc.
+# All Rights Reserved.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+# See LICENSE.md for more details.
+#
+# This file may also be used under the terms of a commercial license
+# if purchased from OpenC3, Inc.
+
+minimumReleaseAge: 1440 # 1 day
+minimumReleaseAgeExclude:
+  # we control these packages, so we don't need to wait to consume them
+  - '@openc3/js-common'
+  - '@openc3/vue-common'